Not sure exactly what capability you&#x27;re referring to with the &quot;famed&quot; scalability, but my point is that CQRS in no way requires Event Sourcing, and offers its own set of benefits. (It&#x27;s also a helluva lot easier to do, or un-do.)<p>In particular, CQRS helps you make a sane architecture for &quot;read models&quot;, where certain features (say, a homepage showing a hard-to-calculate leaderboard) are simple queries against a data-source designed specifically for that feature. The backing data-source is kept up to date by application code as a side-effect of your &quot;real work&quot;.<p>This means you can substantially reduce the runtime load on the database as well as reducing how much application-logic &quot;leaks across&quot; in triggers&#x2F;procedures&#x2F;views. Since your database is often the &quot;bottleneck of last resort&quot;, this means better scalability.