@sargonpiraev

CQRS

#backend

CQRS (Command Query Responsibility Segregation) splits writes (commands) and reads (queries) into separate models and often separate storage paths—so read schemas can be optimized for UI/reporting without contorting the write model. It pairs naturally with event sourcing in some systems but can be adopted lightly (different DTOs, different DB views) without full ES. Cost: more moving parts; use when read/write load or shapes truly diverge, not by default.