Thank you !
середа, 17 серпня 2016 р. 11:10:13 UTC+3 користувач Tal Pressman написав:
>
> Hi,
>
> Our system isn't in production yet, but the current design is:
>
>- The entire system will run on an Akka cluster (with sharding).
>- "Old" entities are passivated after a certain inactivity
Hi,
Our system isn't in production yet, but the current design is:
- The entire system will run on an Akka cluster (with sharding).
- "Old" entities are passivated after a certain inactivity period. At
any given point we expect to have several million live entities.
- The expected
Hi, thanks for info.
May you share some info about your system:
- how many actors do you have per JVM
- how many transactions are kept in memory per actor
- what backend do you use for journal
середа, 17 серпня 2016 р. 09:38:12 UTC+3 користувач Tal Pressman написав:
>
> Hi,
>
> We have
Hi,
We have something similar to the in one of our systems, and the way we did
it is to include the list of processed transactions (IDs) as part of the
actor state. In places where it isn't feasible to keep all transactions in
memory, you can use a bloom filter (if you don't require 100%
