C#•2y ago

Any tooling to help with "event carried state transfer" pattern?

Are there any tooling you use or know for practicing "event carried state transfer" pattern in micro-service/domain service architectures?

How do you deal with situation where you need customer data in 2 different services given they do not share database. And how do you deal with this when you have large system at hand with many of such use cases?

GirtonnenOP•5/14/24, 6:08 PM

I can use message bus to listen to customer created/updated/deleted events, manually persist data in my service db. But I feel like there should be a standardized way of dealing with this, which would also help in case when customer entity is being extended and I need new customer property in downstream service. Or if I spin up new service, would like it to automatically deal with populating my customer "cache" in that new service... Or this tooling could verify that "caches" are indeed valid, and if not, fix them?

GirtonnenOP•5/14/24, 6:09 PM

https://martinfowler.com/articles/201701-event-driven.html Taking definition of "Event-Carried State Transfer" from this M.Fowler's article

martinfowler.com

What do you mean by “Event-Driven”?

Some notes on the different patterns that may be present when people talk about event-driven architectures.