=doc clean up what-is-akka.rst and switch to www.typesafe.com

the latter is necessary because of broken DNS requirements which make
apex domains brittle (since they must resolve to an A record with a
single IP)
This commit is contained in:
Roland Kuhn 2014-03-13 08:54:41 +01:00
parent 05578f564e
commit 98c282f115
28 changed files with 108 additions and 138 deletions

View file

@ -10,7 +10,7 @@ later installed on you machine.
Getting Started Guides and Template Projects
--------------------------------------------
The best way to start learning Akka is to download `Typesafe Activator <http://typesafe.com/platform/getstarted>`_
The best way to start learning Akka is to download `Typesafe Activator <http://www.typesafe.com/platform/getstarted>`_
and try out one of Akka Template Projects.
Download
@ -69,7 +69,7 @@ How to see the JARs dependencies of each Akka module is described in the
Using a release distribution
----------------------------
Download the release you need from http://typesafe.com/stack/downloads/akka and unzip it.
Download the release you need from http://akka.io/downloads and unzip it.
Using a snapshot version
------------------------
@ -117,8 +117,8 @@ Using Akka with Maven
---------------------
The simplest way to get started with Akka and Maven is to check out the
`Typesafe Activator <http://typesafe.com/platform/getstarted>`_
tutorial named `Akka Main in Java <http://typesafe.com/activator/template/akka-sample-main-java>`_.
`Typesafe Activator <http://www.typesafe.com/platform/getstarted>`_
tutorial named `Akka Main in Java <http://www.typesafe.com/activator/template/akka-sample-main-java>`_.
Since Akka is published to Maven Central (for versions since 2.1-M2), is it
enough to add the Akka dependencies to the POM. For example, here is the
@ -139,7 +139,7 @@ Using Akka with SBT
-------------------
The simplest way to get started with Akka and SBT is to check out the
`Akka/SBT template <http://typesafe.com/resources/getting-started/typesafe-stack/downloading-installing.html#template-projects-for-scala-akka-and-play>`_
`Akka/SBT template <http://www.typesafe.com/resources/getting-started/typesafe-stack/downloading-installing.html#template-projects-for-scala-akka-and-play>`_
project.
Summary of the essential parts for using Akka with SBT:
@ -237,7 +237,7 @@ Need help?
If you have questions you can get help on the `Akka Mailing List <http://groups.google.com/group/akka-user>`_.
You can also ask for `commercial support <http://typesafe.com>`_.
You can also ask for `commercial support <http://www.typesafe.com>`_.
Thanks for being a part of the Akka community.

View file

@ -8,20 +8,22 @@
We believe that writing correct concurrent, fault-tolerant and scalable
applications is too hard. Most of the time it's because we are using the wrong
tools and the wrong level of abstraction. Akka is here to change that. Using the
Actor Model we raise the abstraction level and provide a better platform to build
correct, concurrent, and scalable applications. For fault-tolerance we adopt the
"Let it crash" model which the telecom industry has used with great success to
build applications that self-heal and systems that never stop. Actors also provide
the abstraction for transparent distribution and the basis for truly scalable and
fault-tolerant applications.
tools and the wrong level of abstraction. Akka is here to change that. Using
the Actor Model we raise the abstraction level and provide a better platform to
build scalable, resilient and responsive applications—see the `Reactive
Manifesto <http://reactivemanifesto.org/>`_ for more details. For
fault-tolerance we adopt the "let it crash" model which the telecom industry
has used with great success to build applications that self-heal and systems
that never stop. Actors also provide the abstraction for transparent
distribution and the basis for truly scalable and fault-tolerant applications.
Akka is Open Source and available under the Apache 2 License.
Download from http://typesafe.com/stack/downloads/akka/
Download from http://akka.io/downloads.
Please note that all code samples compile, so if you want direct access to the sources, have a look
over at the `Akka Docs Project <@github@/akka-docs/rst>`_.
over at the Akka Docs subproject on github: for `Java <@github@/akka-docs/rst/java/code/docs>`_
and `Scala <@github@/akka-docs/rst/scala/code/docs>`_.
Akka implements a unique hybrid
@ -32,27 +34,28 @@ Actors
Actors give you:
- Simple and high-level abstractions for concurrency and parallelism.
- Asynchronous, non-blocking and highly performant event-driven programming model.
- Very lightweight event-driven processes (approximately 2.7 million actors per GB RAM).
- Simple and high-level abstractions for concurrency and parallelism.
- Asynchronous, non-blocking and highly performant event-driven programming model.
- Very lightweight event-driven processes (several million actors per GB of heap memory).
See :ref:`Actors (Scala) <actors-scala>` and :ref:`Untyped Actors (Java) <untyped-actors-java>`
See the chapter for :ref:`Scala <actors-scala>` or :ref:`Java <untyped-actors-java>`.
Fault Tolerance
---------------
- Supervisor hierarchies with "let-it-crash" semantics.
- Supervisor hierarchies can span over multiple JVMs to provide truly fault-tolerant systems.
- Excellent for writing highly fault-tolerant systems that self-heal and never stop.
- Supervisor hierarchies with "let-it-crash" semantics.
- Supervisor hierarchies can span over multiple JVMs to provide truly fault-tolerant systems.
- Excellent for writing highly fault-tolerant systems that self-heal and never stop.
See :ref:`Fault Tolerance (Scala) <fault-tolerance-scala>` and :ref:`Fault Tolerance (Java) <fault-tolerance-java>`
See :ref:`Fault Tolerance (Scala) <fault-tolerance-scala>` and :ref:`Fault Tolerance (Java) <fault-tolerance-java>`.
Location Transparency
---------------------
Everything in Akka is designed to work in a distributed environment: all
interactions of actors use pure message passing and everything is asynchronous.
For an overview of the remoting see :ref:`remoting`
For an overview of the cluster support see the :ref:`Java <cluster_usage_java>`
and :ref:`Scala <cluster_usage_scala>` documentation chapters.
Persistence
-----------
@ -61,6 +64,8 @@ Messages received by an actor can optionally be persisted and replayed when the
restarted. This allows actors to recover their state, even after JVM crashes or when being migrated
to another node.
You can find more details in the respective chapter for :ref:`Java <persistence-java>` or :ref:`Scala <persistence-scala>`.
Scala and Java APIs
===================
@ -77,45 +82,10 @@ Akka can be used in two different ways
See the :ref:`deployment-scenarios` for details.
What happened to Cloudy Akka?
=============================
Commercial Support
==================
The commercial offering was earlier referred to as Cloudy Akka. This offering
consisted of two things:
Akka is available from Typesafe Inc. under a commercial license which includes
development or production support, read more `here
<http://www.typesafe.com/how/subscription>`_.
- Cluster support for Akka
- Monitoring & Management (formerly called Atmos)
Cloudy Akka has been discontinued and the Cluster support is now being moved into the
Open Source version of Akka (the upcoming Akka 2.1), while Monitoring & Management
(Atmos) has been re-branded as the Typesafe Console, which is now part of the commercial
subscription for the Typesafe Stack (see below for details).
Typesafe Stack
==============
Akka is now also part of the `Typesafe Stack <http://typesafe.com/stack>`_.
The Typesafe Stack is a modern software platform that makes it easy for developers
to build scalable software applications. It combines the Scala programming language,
Akka, the Play! web framework and robust developer tools in a simple package that
integrates seamlessly with existing Java infrastructure.
The Typesafe Stack is all fully open source.
Typesafe Console
================
On top of the Typesafe Stack we also have a commercial product called Typesafe
Console which provides the following features:
#. Slick Web UI with real-time view into the system
#. Management through Dashboard, JMX and REST
#. Dapper-style tracing of messages across components and remote nodes
#. Real-time statistics
#. Very low overhead monitoring agents (should always be on in production)
#. Consolidation of statistics and logging information to a single node
#. Storage of statistics data for later processing
#. Provisioning and rolling upgrades
Read more `here <http://typesafe.com/products/typesafe-subscription>`_.