Alexey Zimarev

For me, it was the security context. This one works in our env. ```yaml apiVersion: apps/v1 kind: StatefulSet metadata: name: acl-eventstore namespace: subs labels: app: acl component: acl-eventstore release: production...

My cluster is GKE. The original message says it's VSphere CSI provider. Every CSI provider is different. If you use the NFS provider, or a local hostpath, you get a...

Thanks! And many thanks for sponsoring the project :)

Basically, the list of original events is already there, added for a different purpose. So, I have more information than I even need. Avoiding deserialization only helps in scenarios when...

Yeah, that's true. I don't agree, though, that it's technical. I'd say that archiving for cheaper storage would work with TTLs. The explicit archive is more business-oriented, like in my...

I hear more people advocating the idea of explicit serialisation when the domain event can use value objects (which is a problem right now, including conversions back and forth in...

I don't think it's possible to easily change it to be configurable, but you are totally right, it should be 500.

You can try adding internal logs: https://github.com/Eventuous/dotnet-sample/blob/7502eccb48c90744a7f2e86151a040aa0c24e199/Bookings/Program.cs#L38

Subscriptions were switched to the normal logger, so any issue should be logged normally within the scope of the subscription logger.

Considering this as low priority as the unprocessed message count can be easily measured by monitoring RMQ queue length from the APM provider side.