CQRS

Turkish equivalent: komut-sorgu sorumluluğu ayrımıDomain: Software Engineering

An architectural pattern that separates models or paths used to change state from those used to read state.

Software-Engineering Context

CQRS does not require separate databases or event sourcing. Its value appears when read and write models have genuinely different scaling, consistency, authorization, or representation needs; otherwise it can add needless synchronization and operational complexity.