playが、なぜnettyからakka-streamにしたいのか？という理由や、モニタリングの話

gistfile1.txt

Hello again,
Thanks again guys for hosting the meetup, it was really great :-)
I promised to get back with some information I wanted to confirm with the team, but in general for example the netty/akka-io question is answered as I hinted at during the meetup:

Please note that these roadmaps are subject to change, as some of the points reach out more than a year ahead,
nevertheless I wanted to let you know of our current plans:

Will play be moving away from netty?
Not in 2.x, there will be both implementations available - akka-streams and netty.
In 3 netty will *most probably*
Why?
As hinted on the meetup, with akka-io we have full control over the threadpools and nitty gritty details of dispatching all events.
We really like netty, but for such a low level project as akka's internals, we'd benefit from having the most control possible on this layer.
Currently we give options to netty, which helps but is not perfect. So there's nothing really "wrong" with netty, we just think we could optimise more if more in control on that layer.

Monitoring solutions?
As I mentioned there's a Tracing SPI being heavily discussed these weeks.
We hope to be able to come to a conclusion soon, which would make 3rd party monitoring solutions hook way better into akka than currently.
No more news here other than we're "on-it".
For now of course there is newrelic and kamon, give it a shot if you'd like to.


I think these were the questions I promised to check with the team, if there's anything else I forgot to respond to please let me know :-)


Thanks for the great meetup (and cow tounge) :-)

-- Konrad