This website uses cookies to ensure you get the best experience.
Learn more.
An application is being split into services with independent data ownership. How should cross-service consistency be designed?
Published
- Define explicit workflows, compensating actions, and consistency expectations across service boundaries.
- Treat message delivery as proof that the business action completed.
- Assume each local transaction automatically commits every remote store atomically.
- Give every service unrestricted access to every other service's tables.
Comments — 0
Sign in to comment