I'm new to akka, since I have some Erlang experience it was looking
familiar for me at first step. We are going to rewrite a SMS
aggregator/gateway whose job is to route messages between different SMSC
endpoints. I'm trying to it with least complexity (akka + camel) without
any Message Broker
AKKA is really Awesome! framework! wonderful!
I'm recently learning AKKA-scala in depth.
Among the AKKA functionalities, DistributedPubSubExtension seems to very
good for me because I'm designing scalable chat server system.
But I have some question about DistributedPubSubExtension when using it
Thanks for sharing! I have create an issue for future investigations:
https://github.com/akka/akka/issues/15784
/Patrik
On Fri, Aug 22, 2014 at 12:31 PM, Sean Zhong clock...@gmail.com wrote:
In case, someone is also looking for the workaround, here is the hacked
implementation
Hi Dave,
we certainly want to provide a proper stream-testkit once streams “go stable”,
here’s a ticket for it: https://github.com/akka/akka/issues/15748
Currently we are reworking the API parts of akka-streams, so the testkit won’t
be shipped in the next minor, but it’s sure to come at some
I think, i have given very less information.
Here is the detailed description
I am using Akka-pull pattern in my project. i am using
akka-contrib_2.10-2.3.4.jar and akka-persistence-experimental_2.10-2.3.4.jar
Front end, master, worker all are running different nodes. The actor system
of
Most systems that store state say ORM and publish events are just really
broken (in a subtle way). They have the problem of two sources of truth
(what if they disagree?)
On Monday, September 1, 2014 6:58:56 AM UTC+1, Ashley Aitken wrote:
Thank you Markus for a very useful contribution.
I
