CQRS
CQRS (Command Query Responsibility Segregation) is an architectural pattern that separates the operations that change data (commands) from the operations that read data (queries) into distinct models, often backed by different data stores.
12 resources across 3 libraries
Glossary Terms(5)
Monolithic Architecture
Monolithic architecture is a software design approach where an entire application — its user interface, business logic, and data access layer — is built and de…
Event-Driven Architecture
Event-driven architecture (EDA) is a software design pattern in which components communicate by producing and consuming events — notifications that something h…
CQRS
CQRS (Command Query Responsibility Segregation) is an architectural pattern that separates the operations that change data (commands) from the operations that…
Saga Pattern
The Saga Pattern is a way of managing data consistency across multiple services in a distributed transaction by breaking it into a sequence of local transactio…
Event Sourcing
Event sourcing is an architectural pattern in which every change to an application's state is captured as an immutable sequence of events, and the current stat…
Study Notes(1)
Interview Questions(6)
What is the CQRS Pattern and When Should You Use It?
CQRS (Command Query Responsibility Segregation) splits the logic and often the data models used for writing data (commands) from the logic and models used for…
What is Event Sourcing and How Does It Differ From Storing Current State?
Event sourcing stores every change to a system's data as an immutable, ordered sequence of events, and derives the current state by replaying those events, rat…
What is CQRS (Command Query Responsibility Segregation)?
CQRS is an architectural pattern that splits a system into two separate models — one for writes (commands) and one for reads (queries) — instead of using a sin…
What is Event Sourcing?
Event sourcing is a pattern where every change to application state is stored as an immutable sequence of events rather than overwriting a single row, and the…
How Do You Design for Read-Heavy vs Write-Heavy Systems?
Read-heavy systems are optimized by aggressively caching and replicating data close to readers so most requests never touch the primary store, while write-heav…
What is the API Composition Pattern?
API composition is a query pattern where a dedicated composer (an API gateway, BFF, or aggregator service) invokes several microservices in parallel or sequenc…