MuleSoft Surat Virtual Meetup#32 - Implementing Command and Query Responsibility Segregation (CQRS) Pattern With MuleSoft
0 likes546 views
MuleSoft Surat Virtual Meetup#32 - Implementing Command and Query Responsibility Segregation (CQRS) Pattern With MuleSoft
More Related Content
What's hot (20)
Similar to MuleSoft Surat Virtual Meetup#32 - Implementing Command and Query Responsibility Segregation (CQRS) Pattern With MuleSoft (20)
More from Jitendra Bafna (20)
Recently uploaded (20)
MuleSoft Surat Virtual Meetup#32 - Implementing Command and Query Responsibility Segregation (CQRS) Pattern With MuleSoft
- 1. Implementing Command and Query Responsibility Segregation (CQRS) Pattern With MuleSoft Surat MuleSoft Meetup Group Jan 14, 2022
- 2. Safe Harbor Statement â—Ź Both the speaker and host are organizing this meet up in individual capacity only. We are not representing our companies here. â—Ź This presentation is strictly for learning purpose only. Organizer/Presenter do not hold any responsibility that same solution will work for your business requirements also. â—Ź This presentation is not meant for any promotional activities.
- 3. A recording of this meetup will be uploaded to events page within 24 hours. Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab. Make it more Interactive!!! Give us feedback! Rate this meetup session by filling feedback form at the end of the day. We Love Feedbacks!!! Its Bread & Butter for Meetup. Housekeeping 3
- 4. 4 Organizers Jitendra Bafna Senior Solution Architect III EPAM Systems Nitish Jain Consultant IBM
- 5. 5 Jitendra Bafna â—Ź14 years of Experience in Integrations and APIs. â—ŹWorking as a Senior Solution Architect III at EPAM Systems. â—ŹMuleSoft Certified Integration and Platform Architect. â—ŹCertified Cloud Architect. â—ŹTOGAF 9.2 Certified â—ŹExpertise in implementing MuleSoft platform like CloudHub, Customer Hosted Mule Runtime, Anypoint VPC, VPN and DLB. â—ŹExpertise in implementing APIs using MuleSoft â—ŹExpertise in Digital Transformation Speaker Jitendra Bafna Senior Solution Architect III EPAM Systems
- 6. Agenda ● What is CQRS? ● Advantages and Disadvantages of CQRS patterns ● Use Cases – CQRS Patterns ● Implementing CQRS With MuleSoft ● Trivia Quiz
- 8. 8 CQRS Integration Pattern âť‘ The Command and Query Responsibility Segregation (CQRS) patterns separates read and write operations to data store. âť‘ Implementing CQRS patterns can enhance the performance, scalability and security. How? âť‘ Commands should be task based, rather than data centric. ("Place Order"). âť‘ Commands may be placed on a queue for asynchronous processing, rather than being processed synchronously. âť‘ Queries never modify the database. A query returns a DTO that does not encapsulate any domain knowledge. âť‘ For greater isolation, the data-stores are physically separate the read data from the write data. âť‘ The data-sync between write and read database is done using master-slave replication on MySQL, however the same can be achieved using ETL tools or Mule Batch programs as well.
- 9. 9 What is Command and Query? âť‘ Command - Modifies data (e.g. Insert, Update & Delete actions) âť‘ Query - Never modifies data (e.g. Select action)
- 11. 11 CQRS Integration Pattern – Use Cases ❑ Scenarios where performance of read operation must be fine tuned independently from the performance of the write operations, especially number of reads is more than writes. ❑ Business rules and SQL queries are complex. ❑ If you want to parallelize the development and use two teams. One team could be assigned to read the model and second one to the write side. ❑ When performance is critical. With CQRS, you can optimize read and write sides independently. ❑ When performance is critical. With CQRS, you can optimize read and write sides independently. ❑ Large projects where high performance is required and independent scalability is required.
- 12. 12 CQRS Integration Pattern – When not to use ❑ No Acceptance of Eventual Consistency. ❑ In case of simple user interface e.g. CRUD style. ❑ When you have simple business logic, then implementation of CQRS would be too overwhelming.
- 13. 13 CQRS Integration Pattern – Advantages ❑ Independent Scaling – In case number of read is more than write operation, read model can be independently scale to get better performance. ❑ Single Responsibility Principle - There are separate models, read & write. It means a method should be either Command or Query. With this separation, you get the Single Responsibility Principle by design. ❑ Separation of Concern – Since there is separate models to read and write data, you can keep complex business logic, validation for write model and keep your read model simple to fetch the data.
- 14. 14 CQRS Integration Pattern – Disadvantages ❑ As there is different read and write model, duplication of code is unavoidable. ❑ There is need to two separate database for read and write model, write database needs to replicate the data in read database, that may leads to eventual consistency. ❑ It adds unnecessary complexity if applications have simple CRUD operations, which can be achieved by traditional architectural styles.
- 15. Experience APIs Process APIs System APIs Queue Event Handler Order Experience API Orders CQRS – API Led Connectivity Customers Orders Details Eventual Consistency Orders Process API Fetch Order Details Write Orders Database Read Orders Database
- 16. 16 References âť‘ https://github.com/mulesoft-catalyst/cqrs-pattern âť‘ https://docs.microsoft.com/en-us/azure/architecture/patterns/cqrs âť‘ https://martinfowler.com/bliki/CQRS.html
- 17. Demonstration
- 18. Q & A
- 19. Quiz Time Get ready to WIN a Special Gift from MuleSoft Community
- 20. Upcoming Meetups â—Ź Dockerization of MuleSoft Clustering â—‹ Sat, Jan 29, 01:00 PM (IST) â—‹ Speaker: Sudeshna Biswas RSVP: https://meetups.mulesoft.com/events/details/mulesoft-surat-presents-dockerization-of-mulesoft- clustering/
- 21. Thank you