Good suggestion. Another alternative is that the AtLeastOnceDelivery actor
rejects new incoming messages when there are too many unconfirmed messages.
That means that the original producer must deal with acknowledgments and
rejections. The AtLeastOnceDelivery actor becomes a safe-handoff point and
Hi Tal,
Thanks for your reply. Your suggestion to use a PersistenceQuery actor
seems like a good one. I'll look into that and let you know.
On Wednesday, August 10, 2016 at 7:57:12 AM UTC+1, Tal Pressman wrote:
>
> Hi,
>
> From what I know, you can't do this using just a single PersistentActor,
Hi,
>From what I know, you can't do this using just a single PersistentActor,
since you have no control of the incoming message rate (even if you just
persist the messages and don't keep them in memory after that, they could
arrive faster than the journal can persist them).
If we assume that