CQRS is an architectural pattern that separates read operations from write operations. In other words, it allows for separate optimization of writing data into a database and reading data from a database. Event sourcing is an architectural pattern that ensures every change to an application's state is recorded as an event. The events are stored in a log or sequence of records that can be used to reconstruct an application's state at any given time. Yes! It is possible to use CQRS without event sourcing; however, there are certain advantages that come with combining these two patterns together. For example, when both CQRS and event sourcing are employed together, developers have more control over which parts of the system need to be updated when making changes—which can help reduce complexity and improve performance by reducing redundant work. Additionally, using both patterns together makes it easier for developers to audit changes made over time by providing visibility into each step of the process.