hanishi commented on issue #2579: URL: https://github.com/apache/pekko/issues/2579#issuecomment-3651027444
For users evaluating it as a simpler alternative to repository-style persistence, small details like recovery boundaries and post-restart hooks can make the difference between “this fits” and “this is confusing”. Event Sourcing isn’t inherently problematic, but it introduces additional complexity around recovery and side effects. For some entities, DurableStateBehavior is sufficient and easier to adopt, particularly for users coming from a traditional repository-based architecture. In those cases, RecoveryCompleted provides a clear boundary indicating when the state is fully available and can be cached or otherwise acted upon as needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
