CQRS Design Pattern Tutorial for Microservices with Examples for Softwar...

CQRS Design Pattern Tutorial for Microservices with Examples for Software Programmers

In this video we will learn about CQRS (Command Query Responsibility Segregation) design pattern for microservices. This is the 3rd design principle in Database design patterns category for microservices. The command query responsibility segregation (CQRS) pattern separates command & query operation for database. You can use the CQRS pattern to separate read and write operations. Use CQRS if there are different performance requirments for throughput, latency, or consistency. Use CQRS design pattern to avoid complex queries like inefficient joins etc. Problem - In monolithic applications, most of time we have 1 database and this database should respond both query and update operations. That means a database is both working for complex join queries, and also perform CRUD operations. But if the application goes more complex this query and crud operations will be also is going to be un-manageable situation. Solution - Solution to above problem is CQRS design pattern. This pattern offers to use “separation of concerns” principles and separate reading database and the writing database with 2 different databases. In this approach, we can even use different database for reading and writing database types like using no-sql for reading and using relational database for crud operations. ** Usage of this Design Pattern ** 1. Use this pattern when to separate out read and write services. 2. Use this pattern when you want to achieve separation of concerns. 3. Use this pattern when you want to scale read and write database independently 4. Use this pattern when you have very high volume of read write operations. ** Advantages of this Design Pattern ** 1. Separate Databases - flexibility to have separate databases for read and write operations. 2. Independent scaling - CQRS allows the read and write workloads to scale independently. 3. Optimized data schemas - the read side can use a schema that is optimized for queries, while the writing side uses a schema that is optimized for updates. 4. Security - It's easier to ensure that only the right domain entities are performing writes on the data. 5. Separation of concerns - Separating the read and write sides can result in models that are more maintainable and flexible. Most of the complex business logic goes into the write model. The read model can be relatively simple. ** Chapter Timestamps ** 0:00 Welcome to CQRS design pattern 1:04 Agenda of tutorial 2:16 Introduction of CQRS design pattern 3:55 Understanding CQRS features 6:22 Real world examples of CQRS design pattern 7:01 Instagram Database Architecture Explained 3:50 Understanding Instagram Database Architecture 8:08 Usage of CQRS design pattern 8:56 Advantages of CQRS design pattern 10:44 Summary of CQRS design pattern 11:37 Next video on CQRS design pattern for microservices #microservices #cqrs #designpatterns ** CHECK OUT OUR OTHER VIDEOS ** Shared Database per Service Design Pattern    • Shared Database P...   Difference between Monolithic and Microservice Architecture    • Difference betwee...   Spring boot project setup:    • Spring boot Proje...   Spring Boot Microservice with postgres database Project:    • Spring Boot Micro...   Prepare Docker file, Container and Build Image:    • Docker Tutorial f...   Deploy Docker Image AWS Elastic Container Service:    • Deploy Springboot...   Solid Principle Tutorial    • Solid Principles ...   ** CHECK OUR PLAYLISTS ** Microservice Architecture and Microservice Design Patterns Tutorial    • Microservice Arch...   Spring Boot Complete Tutorial    • Spring Boot Tutor...   Docker Containers Complete Tutorial    • Cloud & Container...   Solid Principles Tutorial    • Solid Principles ...   Java Design Pattern Complete Tutorial with Examples    • Java Design Patte...   ** ABOUT OUR CHANNEL ** CodeOneDigest is a youtube channel that produces videos on programming languages, cloud and container technologies, Software design principles, Java frameworks in English and Hindi languages. Check out our channel here:    / @codeonedigest   Don’t forget to subscribe! ** OUR WEBSITE ** https://codeonedigest.wordpress.com/ ** GET IN TOUCH ** Email us on codeonedigest@gmail.com FOLLOW US ON SOCIAL - LIKE, SHARE & SUBSCRIBE Get updates or reach out to Get updates on our Social Media Profiles! Subscribe: https://bit.ly/3NeWQ8U Youtube:    / @codeonedigest   Twitter: https://twitter.com/codeonedigest Facebook: https://www.facebook.com/codeonedigest Instagram: https://www.instagram.com/codeonedigest/ Linkedin: https://www.linkedin.com/in/codeone-d... Reddit: https://www.reddit.com/user/codeonedi... Website: https://codeonedigest.wordpress.com/