Hi Team,
I recently noticed this behavior in Akka event-bus and there are different
subscribers listening to events and one subscriber writes to Postgres. This
subscriber retry if the write fails for 10 times with exponential back-off
with max wait of 10 seconds.
Recently we had a postgres out
Hi all. I had this working with java version 2.3.13 and after moving to
2.5.6 it stop working. Let me explain the topology.
In configuration I have
akka.cluster.sharding {
role = "backend"
}
Ok then. If in a process (frontend) I use startProxy and in other process
(backend) I use start in Clus
Thanks Patrik.
I imagine that most savings will come in the area of establishing a connection
as this is completely bypassed with IPC of course.
As an aside, perhaps a functional advantage to supporting IPC is security
though as you can leverage OS permissions.
Cheers
C
> On 30 Oct 2017,
Hi Christopher,
Aeron IPC is currently not supported, but I found it interesting to see if
it works so I tried it. Had to change a few small things. Of course I was
curious about the performance. No difference for small messages (100
bytes), but for 10kB messages it has higher throughput 1100 MB/s
I think you're misunderstanding how this all works. The state lives *in*
the Actor, and is only available while the Actor is live; shutting the
Actors down and starting them so quickly is enormously inefficient. The
database is just a backing store, recording the history of the Actor.
Normally,