System Design: Handle Distributed Transactions | Two-Phase Commit (2PC), Three-Phase Commit (3PC), SAGA Pattern

 

                                        








Synchronous 






Challenge is that if the phase 2 (commit) is failed then consumer is blocked

Synchronous 




SAGA (Saga of Transaction)
Asynchronous 




























Comments

Post a Comment

Popular posts from this blog

Microservice Pattern: SAGA

Image
  Context You are developing a server-side enterprise application. It must support a variety of different clients including desktop browsers, mobile browsers and native mobile applications. The application might also expose an API for 3rd parties to consume. It might also integrate with other applications via either web services or a message broker. The application handles requests (HTTP requests and messages) by executing business logic; accessing a database; exchanging messages with other systems; and returning a HTML/JSON/XML response. There are logical components corresponding to different functional areas of the application. Problem What’s the application’s deployment architecture? Forces There is a team of developers working on the application New team members must quickly become productive The application must be easy to understand and modify You want to practice continuous deployment of the application You must run multiple instances of the application on multiple machines ...
Read more

SQL vs NoSQL | Difference between SQL & NoSQL | SQL Vs NoSQL Tutorial | SQL, NoSQL system design

  SQL  1. Structure          Table,row,column          PreDetermined Schema                    Create table with all the defined datatypes and size.                    Then you can use the table          Relations               1:1,1:M,M:M 2. Nature            Centralized data-all tables in the same database server 3. Scalability          Vertical                     Increase the RAM,Storage         Horizontal -> NOT good for horizontal scaling                    Sharding                      ...
Read more

System Design-Distributed Messaging Queue- RabbitMQ and Kafka

Image
  UseCase: Asynchronous Advantage: Less latency                       UseCase: Retry/Circuit breaker UseCase: Pace matching Point2Point Vs PubSub P2P - one message can be consume by one consumer at a time PubSub- one message can be consumed by many consumers Kafka Architecture Partition 0 in topic A can communicate with only one consumer in CG1 only at a time but it can communicate with other CG2 Cluster Vs ZooKeeper-  list of topics is cluster communication between topics take care by zoo keeper Message:-     Key-      Value- Actual msg -mandatory     Partition-     Topic- mandatory Consumer have below information Consumer No Consumer grp Topic no Partion no Offset no- stating that this mush consumer have read. Use of offset: If the consumer goes down then the next consumer will read the message and check the offset that from where i need to read the message. and henc...
Read more