Core subject of the talk.
Core architectural concept introduced and motivated in the talk.
Question concerns boilerplate in a CQRS architecture.
Discussed alongside event sourcing and DDD.
Asks about CQRS alongside Trailblazer.
EventStorming stickies map directly to commands/events in a CQRS/event-sourced system.
Mentions CQRS among concepts that amazed the speaker.
Slicing write and read sides relies on CQRS for independent development.
References the CQRS pattern when explaining how aggregators shape different views per audience.
The read/write split motivates reading via Active Record and writing via pure aggregates — a CQRS shape.
Briefly covers CQRS with read model and write model as the next pattern after sagas.
Classification project implements 'almost full CQRS' minus a second DB.
Cidurial is explicitly described as a version of CQRS — separate write (commands) and read (SSE) channels.
Attributes the property to the CQRS pub/sub split.
CQRS applies the CQS principle at the service level.
Greg Young coined the term CQRS, first publicly mentioning it on his blog in 2009.
Event sourcing implies a CQRS implementation since query state is derived from events.
Decider composition naturally implements CQRS with command-side decide and query-side evolve.
Separating decision-making write objects from display-oriented read objects is a form of command-query separation.
Partial adoption of CQRS without a second database.
Explicitly presented as a CQRS implementation.