I'll try to answer all questions posted here; It may take more than 1 email, please bear with me :-)
> First of all congratulations on the release of akka-streams and akka-http ! > Thanks! What's a good approach to design such a service ? > All depends on the exact "what should it be doing" I guess. Usually cassandra is used as a datastore accessible by all nodes within *one microservice* that this cluster represents. Different microservices would keep their own databases. Some designs prefer to share a very large cassandra cluster... It all depends on the exact use case I'd say. Full in-depth architecture reviews is something we can do for customers, but sadly not for everyone on akka-user - I'd actually love to, but it's really time consuming for both sides. 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. > I don't think you can / should share "the Context", it's more like an access point to the Spark cluster anyway, right? So each "who needs to submit spark jobs" needs its own context. > 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 ? > The design will be pretty much the same as with Spray based apps. Both are using Akka (actors) internally so the "how to connect with akka cluster" is not really different - find some Spray examples and port them to Http. > For akka streams, we would like to know how to compares with kafka and > storm for example. > It's completely different. It's *not* a distributed stream processing framework. It is a strictly *local* (currently) back-pressure aware way to model streams of data from incoming TCP / Http / or other Reactive Stream data sources. The APIs may look similar (as anything that "looks like the scala collections library"), but the goals and principles behind the tooles you named are completely different. We really want to and eventually will post a blog post and docs about what akka streams are, what they are not, and where they fit etc. Not sure when we'll be able to write that, but it needs doing. > Are there any use-cases where people have used akka streams in place of > kafka ? > No, it's not "instead" – it's "with". Akka Streams are an awesome abstraction to consume logs from and produce them to Kafka, in a backpressured manner, such that you only push as much as you're able to consume etc. -- konrad -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
