You don’t remove things in an event sourced application.
You mark as deleted.
A
B
C
DEL-A
DEL-B
D
DEL-C
— konrad
On 24 November 2014 at 14:08:37, Karthik Chandraraj (ckarthi...@gmail.com)
wrote:
The reason why I used snapshot instead of persist message is, I need to remove
the message from th
The reason why I used snapshot instead of persist message is, I need to
remove the message from the queue on processing it.
In case of snapshot, I will just remove it from the linked queue and save
the snapshot.
How can I achieve the same using persist message?
For ex:
Consider I have received t
Just use persist() to persist messages.
Snapshotting should not be used for every message - it should be used once
in a while.
— konrad
On Fri, Nov 21, 2014 at 7:40 AM, Karthik Chandraraj
wrote:
> Hi,
>
> As per the suggestion, I implemented a QueueActor, which will saveSnapshot
> for every m
Hi,
As per the suggestion, I implemented a QueueActor, which will saveSnapshot
for every message it receives or removed. And then a ProcessActor, which
will read the message from the QueueActor to process it.
Is this the right way to implement durable mailbox with akka-persistence?
Problem I se
Hi Karthik,
akka-persistence does not replace but supersede durable mailboxes. That
means if one wants to have an Actor that does not loose messages upon being
killed then sender must use AtLeastOnce delivery trait (or some other means
of durability with akka-persistence or not) to deliver message
Consider there are 100 messages in the mailbox and the actor is processing
the first.
If the process is killed, what happens to the 99 messages?
When I was searching about this, I came across durable mailboxes, but the
doc says 'durable mailboxes superseded by akka-persistence'.
When I went tho
