Ensuring Eventual Consistency in a Microservices Architecture

How can the architecture of transaction oriented business systems be transformed to a microservices architecture in a “transaction safe” way, where it can be ensured that the system ends up in consistent state?

This paper will introduce a way to ensure eventual consistency in a microservices architecture with irreversible transactions. The paper will promote using a dynamic CAP approach, where the CAP positioning of the system is dynamic based on the concrete business event. Also we will formulate a microservice architectural pattern where the transactional business events are encapsulated in modular micro monoliths.