Akka Community Survey 2016

Dear hakkers,

we did a lot this year already. We merged Akka Streams and HTTP into the 2.4 series of Akka, pushed 16 releases of Akka itself, and maintained the various Persistence plugins. We also reached out to create even more community collaboration with projects related to Kafka, and now are eagerly awaiting codename Alpakka (the various Akka Streams connectors to many different technologies) to take shape and form - all driven by you, the community. We also started this blog, as we wanted to get more in touch with you, on a different level than though raw documentation of Akka–we want to have an ongoing conversation with you.

We want to share more technical details with you and introduce you to the latest happenings. We also started to recognize our most active members of our community by giving out special “happy hakking” t-shirts are unique and you can’t get them anyway else other than becoming a valuable part of our Akka community. These were actually a surprise to many of our contributors, and also, for us, a way to say thanks for all the amazing work these contributors and community as a whole have been doing. But this shouldn’t be the last thing we do this year–in fact, we’re only getting started.

Today, we’d like to announce the “Akka Community Survey 2016”! Its goal is, to make sure to give you, our community, a voice. Of course we’re always on-line and listening to your feedback on the various mailing lists, chats and twitter, however the form of a survey should help us to set direction and see what your thoughts are in a more structured fashion. We compiled a list of questions which will help us to identify missing bits and pieces but also understand better how you are using Akka.

It asks about module usage, your favorite language for Akka, areas of improvements and will take you probably just a short 5 or 10 minutes. We keep it open for a 2 weeks (until September 16th, 2016), and hope to be able to provide you with a nice summary of the results after that.

So, if you have some time to spare and would like to have an impact of Akka’s future:

Take the Akka Community Survey 2016

Aditionally, as a little motivation, we’ll be raffling away 100 Akka t-shirts among the respondents of the survey. Every response who enters the raffle has a chance to win one. The only prerequisite is, that you give us your email address at the end of the survey. You can take this survey anonymously if you don’t want to participate in the raffle. Winners will be notified within two weeks after we closed the survey.

Win an Akka T-Shirt (see more Lightbend swag)

We’re looking forward to your responses. So take the survey, and spread the word!

happy hakking!

-- Markus Eisele & Konrad Malawski
September 01 2016



Past Blog posts
Jan 17 2017
Community Survey 2016 summary While it took us a while to go over the 637 replies replies from the 2016 community survey, now we’re ready to publish a small summary...
Dec 05 2016
We are using Aeron as the underlying transport in the new remoting implementation for Actor messages. The Aeron transport is based on UDP but it provides pretty much the same...
Dec 02 2016
The new remoting implementation for actor messages was released in Akka 2.4.11 two months ago. Artery is the code name for it. It’s a drop-in replacement to the old remoting...
Oct 21 2016
In Mastering GraphStages Part I and Part II we have seen that push and pull are the primary methods to use when implementing a GraphStage. In this post you will...
Sep 23 2016
In part I we have built an XML parser that reads from a streamed data source and emits streamed XML parsing events as its output. This is a bit low...
Sep 16 2016
In previous posts we have shown how to build basic Sinks and Sources, and how to integrate with existing APIs and handle backpressure in various ways. In this post we...
Sep 10 2016
Apache Kafka is the leading distributed messaging system, and Reactive Streams is an emerging standard for asynchronous stream processing. It seems natural to combine these two; that’s why SoftwareMill started...
Sep 05 2016
When working with Akka Streams, one can be assured that all of the data is going to be processed in bounded memory. The reason Akka Streams can guarantee this, is...