Dive into the depths of Command Query Responsibility Segregation (CQRS) as we unravel the history, philosophy, and real-world applications of this architectural style. CQRS promises a separation of concerns, but does it also necessitate the separation at the persistence level? We will critically examine the distinction between read and write models supporting CQRS. By the end of this talk, you'll be armed with the insights to determine if, when, and why two databases might be just what your project needs — or not.

Key takeaways:

* Grasp the origins and motivations behind the CQRS
* Understand the intricacies of separating read and write models on the database level
* Equip yourself with criteria and guidelines to make informed decisions on whether employing one or two databases is the right choice