Hi, First of all congratulations on the release of akka-streams and akka-http !
I am writing a service and spray was my initial choice but with akka-http and spray merge I am more inclined to start learning and using akka-http. This service needs to manage a SparkContext and most likely Cassandra and ElastiSearch. SparkContext needs a dedicated master to start the job over a cluster manager like yarn / mesos that manages the workers while Cassandra works over a gossip protocol on a pool of nodes (I think it can be run on Mesos as well). akka clustering also uses a gossip protocol. What's a good approach to design such a service ? I run a akka-http with clustering so that as load grows the service moves from running on one node to running on 10 nodes but now each node will maintain a separate spark context. I am not sure how can I share a spark context over a akka-http running using clustering. Most likely each node will maintain a separate spark context and that makes sense since the load grew from 10000 users to 100000 users for example. The underlying data access can be shared through off heap storage like tachyon. Also are there examples on using akka-http with clustering ? Spray had examples of running a spray service on multiple nodes. The same example will be valid for akka-http as well ? Pointers on using akka-http with clustering will be really helpful. For akka streams, we would like to know how to compares with kafka and storm for example. Are there any use-cases where people have used akka streams in place of kafka ? akka stream is scala and most likely we can score a spark mllib model directly using features from akka-stream and there is no need to use DStream API as such. Is a connector available for akka-stream to Spark ? It will be great if we can extract storm style streaming latency using akka-stream ! Thanks. Deb On Wednesday, July 15, 2015 at 5:40:25 AM UTC-7, Konrad Malawski wrote: > > Dear hakkers, > > we—the Akka committers—are very pleased to announce the final release of > Akka Streams & HTTP 1.0. After countless hours and many months of work we > now consider Streams & HTTP good enough for evaluation and production use, > subject to the caveat on performance below. We will continue to improve the > implementation as well as to add features over the coming months, which > will be marked as 1.x releases—in particular concerning HTTPS support > (exposing certificate information per request and allowing session > renegotiation) and websocket client features—before we finally add these > new modules to the 2.4 development branch. In the meantime both Streams and > HTTP can be used with Akka 2.4 artifacts since these are binary backwards > compatibility with Akka 2.3. > A Note on Performance > > Version 1.0 is fully functional but not yet optimized for performance. To > make it very clear: Spray currently is a lot faster at serving HTTP > responses than Akka HTTP is. We are aware of this and we know that a lot of > you are waiting to use it in anger for high-performance applications, but > we follow a “correctness first” approach. After 1.0 is released we will > start working on performance benchmarking and optimization, the focus of > the 1.1 release will be on closing the gap to Spray. > What Changed since 1.0–RC4 > > - > > Plenty documentation improvements on advanced stages > <https://github.com/akka/akka/pull/17966>, modularity > <https://github.com/akka/akka/issues/17337> and Http javadsl > <https://github.com/akka/akka/pull/17965>, > - > > Improvements to Http stability under high load > <https://github.com/akka/akka/issues/17854>, > - > > The streams cook-book translated to Java > <https://github.com/akka/akka/issues/16787>, > - > > A number of new stream operators: recover > <https://github.com/akka/akka/pull/17998> and generalized UnzipWith > <https://github.com/akka/akka/pull/17998> contributed by Alexander > Golubev, > - > > The javadsl for Akka Http <https://github.com/akka/akka/pull/17988> is > now nicer to use from Java 8 and when returning Futures, > - > > also Akka Streams and Http should now be properly packaged for OSGi > <https://github.com/akka/akka/pull/17979>, thanks to Rafał Krzewski. > > The complete list of closed tickets can be found in the 1.0 milestones of > streams <https://github.com/akka/akka/issues?q=milestone%3Astreams-1.0> > and http <https://github.com/akka/akka/issues?q=milestone%3Ahttp-1.0> on > github. > Release Statistics > > Since the RC4 release: > > - > > 32 tickets closed > - > > 252 files changed, 16861 insertions (+), 1834 deletions(-), > - > > … and a total of 9 contributors! > > commits added removed > > 26 2342 335 Johannes Rudolph > 11 10112 97 Endre Sándor Varga > 9 757 173 Martynas Mickevičius > 8 2821 487 Konrad Malawski > 3 28 49 2beaucoup > 3 701 636 Viktor Klang > 2 43 7 Rafał Krzewski > 2 801 42 Alexander Golubev > 1 8 8 Heiko Seeberger > > -- > > Cheers, > > Konrad 'ktoso’ Malawski > > Akka <http://akka.io/> @ Typesafe <http://typesafe.com/> > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
