Dear hakkers,
We’re excited to announce that we have released the first development
milestone of the new Akka Remoting, which has the code named Artery. It’s
an early development preview and we encourage you to try it out and give us
feedback, but it’s not intended for production usage yet.
The version number is 2.4-ARTERY-M1 with same artifacts as usual.
It is enabled with the following configuration:
akka.remote.artery {
enabled = on
# The hostname or ip clients should connect to.
hostname = localhost
# use 0 if you want a random available port
port = 20200
}
The protocol part of the actor system address is artery (*), so you need to
change previous akka.tcp to artery in for example configuration of cluster
seed-nodes.
The key features of Artery compared to current implementation will be:
-
support high throughput and low latency, such as 1,000,000 msg/s and
sub-millisecond latency (more details in the design document
<https://github.com/akka/akka-meta/issues/16>, and no hard promises yet)
-
improved cluster stability by using isolated streams for control
messages, this means less false failure detection in case of heavy message
traffic
-
reduce message envelope overhead by smart compression of actor
references and other header information
-
make it possible to use efficient serialization with ByteBuffers directly
-
protocol stability between major Akka versions to support for example
rolling upgrade deployments (the protocol is however incompatible with
current TCP based protocol)
-
internal design that is easier to maintain
We are using Aeron <https://github.com/real-logic/Aeron> as the underlying
transport and are implementing the layers on top using Akka Streams. You
find more details in the design document
<https://github.com/akka/akka-meta/issues/16>.
The development branch is artery-dev
<https://github.com/akka/akka/tree/artery-dev>, in case you want to take a
look or contribute. Issues are labeled with t:remoting:artery
<https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Aremoting%3Aartery>
.
Cheers,
Akka Team
(*) The protocol name is not final and may change before the new remoting
infrastructure goes stable.
--
Patrik Nordwall
Akka Tech Lead
Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM
Twitter: @patriknw
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
