3 ms·
Thank you, that makes sense and a lot more clear to me. Now I only wish there would be a good alternatives for when you want to have multiple instances per agg
by valenterry 5y ago
Thank you, that makes sense and a lot more clear to me.
Now I only wish there would be a good alternatives for when you want to have multiple instances per aggregate (even if you may have to give up certain guarantees).
- dharmaturtle 5y agoInteresting... just to be clear, an _individual stream of user events_ is an aggregate. E.g. a user Bob Smith's events are independent of another user like Jane Doe. It isn't the case that the entire "User Table" is a single aggregate - each row in it is an aggregate. If you're trying to do multimaster db storage, like a phone app syncing with some cloud server, where an aggregate resides in two separate locations, this is where event sourcing shines. It's just like git, right, and so you can do all the stuff that git can do - merge event streams, rebase events... it's actually the reason why my pet project switched from an RDBMS to event sourcing. Related video: https://skillsmatter.com/skillscasts/1980-cqrs-not-just-for-server-systems https://skillsmatter.com/skillscasts/1980-cqrs-not-just-for-...
- Salgat 5y agoYou can run multiple instances, and use something like distributed locks to avoid contention causing failures.