DOC: Removed stability-matrix
This commit is contained in:
Patrik Nordwall
parent
531397edc2
commit
b500f4af3a
16 changed files with 1 additions and 60 deletions
1
.gitignore
vendored
1
.gitignore
vendored
|
|
@ -59,3 +59,4 @@ akka.sublime-project
|
|||
akka.sublime-workspace
|
||||
.target
|
||||
.multi-jvm
|
||||
_mb
|
||||
|
|
|
|||
|
|
@ -11,4 +11,3 @@ Additional Information
|
|||
companies-using-akka
|
||||
third-party-integrations
|
||||
language-bindings
|
||||
stability-matrix
|
||||
|
|
|
|||
|
|
@ -1,33 +0,0 @@
|
|||
Feature Stability Matrix
|
||||
========================
|
||||
|
||||
Akka is comprised of a number if modules, with different levels of maturity and in different parts of their lifecycle, the matrix below gives you get current stability level of the modules.
|
||||
|
||||
Explanation of the different levels of stability
|
||||
------------------------------------------------
|
||||
|
||||
* **Solid** - Proven solid in heavy production usage
|
||||
* **Stable** - Ready for use in production environment
|
||||
* **In progress** - Not enough feedback/use to claim it's ready for production use
|
||||
|
||||
================================ ============ ============ ============
|
||||
Feature Solid Stable In progress
|
||||
================================ ============ ============ ============
|
||||
Actors (Scala) Solid
|
||||
Actors (Java) Solid
|
||||
Typed Actors (Scala) Solid
|
||||
Typed Actors (Java) Solid
|
||||
STM (Scala) Solid
|
||||
STM (Java) Solid
|
||||
Transactors (Scala) Solid
|
||||
Transactors (Java) Solid
|
||||
Remote Actors (Scala) Solid
|
||||
Remote Actors (Java) Solid
|
||||
Camel Solid
|
||||
AMQP Solid
|
||||
HTTP Solid
|
||||
Integration Guice Stable
|
||||
Integration Spring Stable
|
||||
Scheduler Solid
|
||||
Redis Pub Sub In progress
|
||||
================================ ============ ============ ============
|
||||
|
|
@ -4,8 +4,6 @@
|
|||
Duration
|
||||
########
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
Durations are used throughout the Akka library, wherefore this concept is
|
||||
represented by a special data type, :class:`Duration`. Values of this type may
|
||||
represent infinite (:obj:`Duration.Inf`, :obj:`Duration.MinusInf`) or finite
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ HTTP
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
When deploying in a servlet container:
|
||||
--------------------------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ Software Transactional Memory (Java)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
Overview of STM
|
||||
---------------
|
||||
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ Transactors (Java)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
Why Transactors?
|
||||
----------------
|
||||
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ Transactors (Scala)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
Why Transactors?
|
||||
----------------
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@
|
|||
Spring Integration
|
||||
####################
|
||||
|
||||
Module stability: **STABLE**
|
||||
|
||||
Akkas integration with the `Spring Framework <http://www.springsource.org>`_ supplies the Spring way of using the Typed Actor Java API and for CamelService configuration for :ref:`camel-spring-applications`. It uses Spring's custom namespaces to create Typed Actors, supervisor hierarchies and a CamelService in a Spring environment.
|
||||
|
||||
Contents:
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ Dispatchers (Java)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
The Dispatcher is an important piece that allows you to configure the right semantics and parameters for optimal performance, throughput and scalability. Different Actors have different needs.
|
||||
|
||||
Akka supports dispatchers for both event-driven lightweight threads, allowing creation of millions threads on a single workstation, and thread-based Actors, where each dispatcher is bound to a dedicated OS thread.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,6 @@
|
|||
Guice Integration
|
||||
=================
|
||||
|
||||
Module stability: **STABLE**
|
||||
|
||||
All Typed Actors support dependency injection using `Guice <http://code.google.com/p/google-guice/>`_ annotations (such as ‘@Inject’ etc.).
|
||||
The ‘TypedActorManager’ class understands Guice and will do the wiring for you.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ Typed Actors (Java)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
The Typed Actors are implemented through `Typed Actors <http://en.wikipedia.org/wiki/Active_object>`_. It uses AOP through `AspectWerkz <http://aspectwerkz.codehaus.org/>`_ to turn regular POJOs into asynchronous non-blocking Actors with semantics of the Actor Model. Each method dispatch is turned into a message that is put on a queue to be processed by the Typed Actor sequentially one by one.
|
||||
|
||||
If you are using the `Spring Framework <http://springsource.org>`_ then take a look at Akka's `Spring integration <spring-integration>`_.
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ Agents (Scala)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
Agents in Akka were inspired by `agents in Clojure <http://clojure.org/agents>`_.
|
||||
|
||||
Agents provide asynchronous change of individual locations. Agents are bound to a single storage location for their lifetime, and only allow mutation of that location (to a new state) to occur as a result of an action. Update actions are functions that are asynchronously applied to the Agent's state and whose return value becomes the Agent's new state. The state of an Agent should be immutable.
|
||||
|
|
|
|||
|
|
@ -7,8 +7,6 @@ Dispatchers (Scala)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
The Dispatcher is an important piece that allows you to configure the right semantics and parameters for optimal performance, throughput and scalability. Different Actors have different needs.
|
||||
|
||||
Akka supports dispatchers for both event-driven lightweight threads, allowing creation of millions of threads on a single workstation, and thread-based Actors, where each dispatcher is bound to a dedicated OS thread.
|
||||
|
|
|
|||
|
|
@ -14,8 +14,6 @@ FSM
|
|||
.. versionchanged:: 1.2
|
||||
added Tracing and Logging
|
||||
|
||||
Module stability: **STABLE**
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
|
|
|
|||
|
|
@ -5,8 +5,6 @@ Typed Actors (Scala)
|
|||
|
||||
.. contents:: :local:
|
||||
|
||||
Module stability: **SOLID**
|
||||
|
||||
The Typed Actors are implemented through `Typed Actors <http://en.wikipedia.org/wiki/Active_object>`_. It uses AOP through `AspectWerkz <http://aspectwerkz.codehaus.org/>`_ to turn regular POJOs into asynchronous non-blocking Actors with semantics of the Actor Model. Each method dispatch is turned into a message that is put on a queue to be processed by the Typed Actor sequentially one by one.
|
||||
|
||||
If you are using the `Spring Framework <http://springsource.org>`_ then take a look at Akka's `Spring integration <spring-integration>`_.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue