The CAP Theorem describes three safety properties: data consistency, availability, and node or partition tolerance in distributed systems. In fact, applying the database-per-service pattern in a microservice environment will entail new challenges to manage transactions. So, what about two-phase commit? It will affect the cap pairs, since it is blocking in nature. First of all, the 2-pc coordinator will present a spoof and will attack the availability node and it is not supported by message brokers or newly released NoSQL databases, etc.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

tutorial,microservices,soa,software architecture,distributed systems,cqrs