Distributed Transactions through an Order System

Transitioning from Monolithic to MSA and Distributed Transactions

As services grow and become more complex, many companies find themselves considering a transition from traditional Monolithic architecture to Microservices Architecture (MSA). MSA is a modern architecture that ensures independence and scalability between services, enabling rapid development and deployment, as well as flexible failure response. However, this transition comes with important challenges that must be addressed. That is the issue of transaction consistency and integrity.

In a monolithic environment, transaction management was relatively simple because all processing could be performed within a single database and transaction boundary. Data from various domains such as orders, payments, and inventory were bundled into one transaction and processed consistently. However, with the transition to MSA, each domain is separated into independent services with separate databases, creating a situation where it becomes difficult to guarantee data consistency with traditional transaction processing methods.

In this lecture, we learn about how to solve transaction problems in MSA environments that cannot be resolved with single transactions, focusing on distributed transaction patterns: 2PC, TCC, and SAGA.

In particular, this course doesn't stop at simple theoretical explanations, but centers around an order service, starting from a Monolithic structure and transitioning to an MSA environment to show what problems actually occur in practice, and how these can be solved through each pattern, explained with specific flowcharts, example code, and practical application tips.

After taking the course

• I understand the transaction issues that occur when transitioning from Monolithic to MSA.

• You can learn about the structure, advantages and disadvantages, and considerations for applying each distributed transaction pattern.

• You can learn design strategies for ensuring transaction consistency in real-world applications.

• You can control concurrency using Lock.

  
  

Pre-enrollment Reference Information

Precautions

• This course is not a course on building an order system, but rather a course that explores distributed transactions used in MSA environments using a very simple order system as an example.

  • For example, it does not cover features such as payment processing using payments that could be utilized for orders.