Alexander Berl

Hmm, I'm not sure tbh. I think the default itself is sane. If nothing is in the AppliedEventsLog, it should be assumed that it's a completely new Listener that needs...

Here's an idea we came up with at the weekly: Processes have the very clear concept of a lifecycle, as is described in e.g. https://leanpub.com/esversioning/read#leanpub-auto-versioning-process-managers. This means that a Process...

What a bummer :/ Sorry that happened (again). Would the last point have avoided the issue? Afais it would, no? > Only change `AbstractAsynchronousProcessManager::getHighestAppliedSequenceNumber()` to return the current store sequenceNumber...

> I like the notion of a "durable name" Yes, this is a very core concept of pubsub systems and basically what we do already with async EventListeners (and hence...

> A CLI Command ;) Dang! Unubiquitous language > Edit: Nevermind, you meant #141 (comment) I assume ;) Exactly :) > Uh no? Yeah, "do not do the same work...

Addition regarding > Only change AbstractAsynchronousProcessManager::getHighestAppliedSequenceNumber() to return the current store sequenceNumber if 0 is returned from the appliedEventsLogRepository, since this somehow makes sense as default for ProcessManagers (only) This...

> 1. Make correlationId a core concept That would be a good thing I guess. We need to take care of two things though: - Adding `EventWithCorrelationId` will probably lead...

> FSM? Fliegendes Spaghettimonster? :) Finite State Machine. But the Spaghettimonster sometimes would fit too ;) > The state is not "manually" reconstituted via some Repository::get() call, but upon every...

Hey there, nice to know this is still finding people :) And you're absolutely right in that being able to convert to the model format is pretty important for this...

> I managed to construct a simple .trim file (a white cube) in NASM (yes, I created a binary file in an assembler, don't judge me): Haha. I won't. That's...