CQRS is usually shown as the pattern that adds too much overhead. People wrongly assume that it can be used only in enterprise projects. In a nutshell, CQRS is a structural pattern that shows how to structure your architecture. You need to slice it by the behaviour: business logic and queries. I'll explain where those myths about multiple databases, eventual consistency and event sourcing come from. I'll show CQRS as it is, so simple pattern that allows on-point optimisation and easier evolution.