CQRS Without the Astronaut Architecture

A practical guide to implementing CQRS (Command Query Responsibility Segregation) in Node.js/TypeScript without the heavy infrastructure often associated with it. The post argues that CQRS is fundamentally a code organization pattern — splitting read and write paths into separate classes — not a requirement for event sourcing, multiple databases, or message queues. It walks through concrete TypeScript examples showing a rich write side (commands with domain logic) and a lean read side (direct SQL queries returning flat DTOs), discusses optional typed CommandBus/QueryBus patterns, and provides clear guidance on when to use or skip CQRS. The post also outlines a scaling ladder from simple code-level separation up to event sourcing, advising teams to start at step 1 and only climb when metrics demand it.