[akka-user] There are now akka-stream in master. Why?
I just have noticed master hasn't anymore akka-stream subproject. Does it mean akka (and Scala in whole) reactive streaming is preparing for the next reincarnation? :) -- 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.
Re: [akka-user] There are now akka-stream in master. Why?
Uhm, I don’t think it ever had streams in it, hm! :-) The streams are in active development and are located in the release-2.3-dev branch. Slightly hidden we know, on the other hand, it’s very aggressively changing, so that may be a good thing… Anyhow, you’re free to give it a spin! Feedback is also very welcome. Happy hakking! -- Konrad 'ktoso' Malawski hAkker @ typesafe -- 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.
[akka-user] Re: There are now akka-stream in master. Why?
Sorry, my mistake, I mean There are *no* akka-stream I haven't found a way to edit the subject. -- 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.
Re: [akka-user] There are now akka-stream in master. Why?
No worries, https://github.com/akka/akka/tree/release-2.3-dev/akka-stream Happy hakking :-) -- Konrad 'ktoso' Malawski hAkker @ typesafe -- 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.
Re: [akka-user] There are now akka-stream in master. Why?
Yes, perhaps I should explain our current workflow with these branches actually: master will eventually become akka 2.4.x release-2.3 will eventually become akka 2.3.4 (and 2.3.5 if it’s needed etc). release-2.3-dev is used only for streams development. It is separate to keep iterating / releasing streams faster than the main akka 2.3. It will be merged to release-2.3 once we decide they’re ready to roll-in. Needed changes from 2.3 will be ported to 2.4 (master), of course at some point. I hope this helps! -- Cheers, Konrad 'ktoso' Malawski hAkker - Typesafe, Inc http://scaladays.org -- 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.
[akka-user] Current Best Practices for CQRS with Akka?
Howdy All, I've been reading lots of threads on the Akka User mailing list and pull requests and blog posts within the community but I am confused about what currently are the best practices for: 1. Distributed and Resilient Pub-Sub within Akka It seems to me that a resilient pub-sub is a key component for a CQRS approach and for a distributed system this would also need to be distributed. I believe the event system in Akka is currently per-node and not resilient. What is the current best practice for resilient distributed pub-sub for CQRS with Akka? Please note the best practice may be to use a third-party distributed and resilient pub-sub technology and I am open to that (but I would prefer to stay with something within Akka or the Typesafe platform). 2. Process Managers What is the best approach to implementing process managers (for sagas) in CQRS with Akka. I am quite a novice in this area so the answer may be obvious but I'm wondering about whether it's best to use singleton actors, processors, eventsourced processors, finite state machine etc. It seems to me that process managers in a distributed system would also require distributed and resilient pub-sub (as discussed above) to work well. 3. Denormalisation of Views I've discussed this previously with Martin and others as a result of the restriction of Views to track one processor. Ideas like using a database with triggers within the view model to update denormalised data were suggested but I am wondering if this is the best practice for now? I'm thinking that again distributed and resilient pub-sub (as discussed above) may be another way to achieve this. Sorry if I have missed some crucial documentation or posts. I've probably seen most discussion relating these to the questions but I'm somewhat confused as some of the posts are older and others discuss solutions without Akka Persistence (I think). Thanks in advance for any suggestions. Cheers, Ashley. -- 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.
