Implementing Microservices architecture introduces certain operational challenges. One of the most common is: decentralized data management and embedding dependencies. In this talk at APIDays London (Banking APIs) Irakli discussed three powerful tools you can use to help with the challenge.
High Cohesion is why Bounded Contexts are critical
High Cohesion is why Bounded Contexts are critical
High Cohesion is why Bounded Contexts are critical
You cannot execute an ACID transaction because there is no way Marriot, US Airways and Hertz would allow me to put a lock on their back-end databases.
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
Hector Garcia Mollina and
http://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
You do not get transactions, because each microservices encapsulates its own data storage.
long-lived distributed transactions.
lightweightness is one benefit
another one – better portability (at least for now), VMs are not very portable