Hi folks,
I am just starting with event sourcing and still struggle to get domain
problems solved. Maybe a user database is not a good fit for ES, dunno :)
What do I want to achieve:
* Users can be created (having an immutable UUID and an email which is used
as username)
* Email can be
Have chatted with @ktoso about this and seems, that my thoughts are not
totally wrong. Will create a ticket on GitHub for that.
Am Donnerstag, 23. Juni 2016 22:27:45 UTC+2 schrieb Christian Hoffmeister:
>
> Hi,
>
> I have a sample application where two nodes join an Akka cluster. On both
>
Ok, my assumption is right
(see
https://github.com/akka/akka/blob/master/akka-cluster-tools/src/main/scala/akka/cluster/pubsub/DistributedPubSubMediator.scala#L669).
Is there a way to work around this? I don't want to wait some random time
interval after leaving before actually shutting down.
Hi,
I have a sample application where two nodes join an Akka cluster. On both
nodes there is an actor running registered to DistributedPubSubMediator and
both are sending a Ping once per second (that hits either itself or the
other node).
Then I gracefully shut down Node B (leave cluster,
So basically the known seed nodes are replaces with a known etcd cluster
for the information sharing, if I understand this right?
Somewhat like this?
* A joins, no one is there, so it puts inself into etcd and starts a single
node cluster
* B joins, finds A in etcd and joins A
* C joins, finds
Hello,
I am just starting to dive into akka-cluster and have a question regarding
the seed nodes:
My test project consists of 4 projects so far:
* PROTOCOL contains messaging case classes
* API contains cluster node, that also exposes a rest api (akka-cluster +
akka-http)
* AUTH contains
