Re: [akka-user] Re: Akka remote communication roadmap?

If I have to give up on Akka remote because it is slow, I'll just switch to something like Vert.x, not sure what's going on here or why it has such little importance when it is part of Akka selling speech: "Location transparency" or is it only an advertisement but not used much in practice

Re: [akka-user] Re: Akka remote communication roadmap?

Current main focus is getting Akka Streams and Akka Http ready for prime time. In case someone is able/willing to take a stab at starting the migration of Akka Remote to Akka Streams right now, I'd love to advise / review etc but I have no spare cycles at the moment to do any actual work on it.

Re: [akka-user] Re: Akka remote communication roadmap?

Hi Viktor, Maybe you could abstract the transport API and create multiple implementations, with both Netty and Aeron, Aeron might not be as fast as you think, some performance benchmark on different transports and keep a updated score table to keep the user informed on what transport works

Re: [akka-user] Re: Akka remote communication roadmap?

Hi Guido, Would you be interested in contributing towards this? On Thu, Oct 15, 2015 at 11:02 AM, Guido Medina wrote: > Hi Viktor, > > Maybe you could abstract the transport API and create multiple > implementations, with both Netty and Aeron, Aeron might not be as fast as >

Re: [akka-user] Re: Akka remote communication roadmap?

If that was my expertise I would at definitely done something already, but the only thing I have done with Netty is a TCP server for a logger hardware for the utility industry, nothing that would require such level of details like someone with hands on NIO, Scala and Serialization altogether.

Re: [akka-user] Re: Akka remote communication roadmap?

Git URL correction: https://github.com/hepin1989/akka-remote-transport-netty4 On Thursday, October 15, 2015 at 10:54:46 AM UTC+1, Guido Medina wrote: > > If that was my expertise I would at definitely done something already, but > the only thing I have done with Netty is a TCP server for a

[akka-user] Re: Akka remote communication roadmap?

Very nice, I wasn't aware of it, IMHO it needs something like that as proper remote communication is the foundation for distributed micro-services, our application is a FOREX trading application and we might eventually move to high-frequency trading, it is in production and for what we do at

[akka-user] Re: Akka remote communication roadmap?

Did you see this? https://github.com/typesafehub/netty-reactive-streams/blob/master/pom.xml I think it's a first step of migration to streams. It already depends on Netty 4. On Wednesday, October 14, 2015 at 12:22:33 PM UTC+3, Guido Medina wrote: > > Hi, > > I created a similar post some time

Re: [akka-user] Re: Akka remote communication roadmap?

For extremely low latency we'd want to use a transport like Aeron. On Wed, Oct 14, 2015 at 1:34 PM, Guido Medina wrote: > Very nice, I wasn't aware of it, IMHO it needs something like that as > proper remote communication is the foundation for distributed > micro-services,