Alexey Zimarev
Alexey Zimarev
For all the available stores (relational and ESDB) add tests to ensure that the subscription drop causes resubscribe. Also ensure that the health check returns degraded when the subscription is...
55K events produced and consumed in parallel - Checks the last event's global position and ensures it's the number of produced messages minus one - Ensures that the checkpoint is...
Proposal: - Place the loaded aggregate instance in a cache - When getting a command for that instance, get it from the cache instead of loading it from the stream...
I get lots of questions about process managers. Personally, I am not a big fan because: * Processes are indeed everywhere * Most processes are natural and not orchestrated *...
How to make subscriptions work in a serverless world? ### Simplest scenario: monolithic deployment The whole application represents a single bounded context, where commands and queries are combined into a...
Ensure that it is possible to override the exchange name for the gateway producer and have a more fine-grained configuration for the subscription. You can already specify the exchange, but...
When a subscription is deployed as a serverless function or container, it's hard to control how many instances are currently active. It will inevitably lead to multiple instances running simultaneously,...
For a while, I advocated treating events as contracts and keeping them clean of sophisticated types like value objects. It solves the issue of serialisation as it should work unconditionally,...
ESDB has this smart functionality that allows maintaining less subscriptions if all the event handlers are live. In Eventuous context it would work like this: * Each subscription (group of...
Fixes #176