recall

← recall

command-query responsibility segregation concept

Reads and writes have different shapes: different consistency requirements, different scaling characteristics, different access patterns.

Reads and writes have different shapes: different consistency requirements, different scaling characteristics, different access patterns. CQRS separates them into distinct models so each can be optimized independently. Often paired with event sourcing — writes append to an event log, reads project from materialized views derived from that log. The cost is more moving parts and eventual consistency between them; the payoff is reads and writes that scale on independent dimensions.

Reads and writes have different shapes — different consistency requirements, different scaling needs, different access patterns. CQRS splits them so each can be optimized independently.

see also

aliases: CQRS

topics: architecture

references: