Proto Eventuous integration about eventuous HOT 2 OPEN

The question is from which side this to be approached.

• The current proto persistence has nice features like snapshot strategies. I have not implemented snapshotting yet, but if I do, it might not support strategies other than event count.
• I currently only plan to support ESDB adapters as this is an application-oriented library, with a focus on apps with proper domain models. Therefore, I need subscriptions. The IEventStore interface is trivial to implement for other databases, but I don't see how it fits the library.
• I want to have Proto.Actor integration from the application side. For example, implement an application service as an actor.

I agree that handling backpressure on the database properly is a good feature to build anyway, as even a normal system might struggle under peak load.

from eventuous.

Maybe I haven't made my point clear enough... Eventuous is not a tech lib for shovelling events to the store, it's a library to build business apps with tactical DDD, Event Sourcing and CQRS. We can discuss if the case of Proto.Persistence alone can fit here, and how.

Still, my plan to use Proto.Actor from the application side is very real.

from eventuous.