Alexey Zimarev
Alexey Zimarev
It's infrastructure-specific, but we need a way to perform an operation on new streams using the native event store client feature, like setting the stream meta using `EventStoreClient`. It can...
In order to keep the database size in an event store upper bound, it would be useful to bake the archiving function. The archive storage could be anything, so it...
There's a package to add retries using Polly to subscriptions (for retrying event handlers). However, we need more places with retries, and there's no need for complex policies that Polly...
Right now, the event store is agnostic to what events are being persisted. It is quite a limitation for doing things like #64, domain-driven snapshots, closing periods, etc, as some...
Thinking about what to add to the default meta. - Event source: - Aggregate type (as it's not necessarily encoded in the stream name) - Application name - Application version...
Related to #77 @thomaseyde describes that the application service fails when handling a command when an event stream contains an unknown event. Currently, the app service returns an `ErrorResult` where...
Similar to RMQ
The `AllStreamSubscriptionService` accepts the filter, so it's possible to limit the number of events delivered. It works fine, but it must be explicitly configured. As we don't really know what...
- [x] `TypedEventHandler` - [ ] `AggregateState` with explicit handlers - [x] `MongoProjection` when it supports registering handlers
There's no _gap_ for RMQ, but lead-time is relevant. Also, a subscription queue size basically tells how many events aren't processed. RMQ management API could help. The limitation is that...