Dear hakkers,

We’re excited to announce that we have released the second 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-M2 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.

A summary of what is included in M2 compared to M1
<https://groups.google.com/d/msg/akka-user/z05q9-cEULw/qCJqqYlwAAAJ>:


   -

   performance improvements
   -

   initial flight recorder to capture low and high frequency events in
   memory mapped files for debugging (also production issues) and testing
   -

   make it possible to use efficient serialization with ByteBuffers directly
   -

   various bug fixes, including issues with remote deployment
   -

   test coverage by porting most of the old remoting tests


The full list of changes since the last milestone is available under the
2.4-ARTERY-M2
<https://github.com/akka/akka/issues?q=milestone%3A2.4-ARTERY-M2+is%3Aclosed>
milestone on github for your reference.

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>
.

(*) 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.

Reply via email to