Most systems today use CRUD: read the current state, modify a row, write it back. The database remembers where things
Continue readingEvent Sourcing in Practice: Building a System That Never Forgets
Most applications start with a simple mental model: one database, one set of tables, and CRUD operations that read and
Continue readingCQRS in Practice: Splitting Reads and Writes for Scalable Systems
CQRS and Event Sourcing: Building an Order System from Scratch in Go Most of us build CRUD services by default:
Continue readingCQRS and Event Sourcing: Building an Order System from Scratch in Go
Most applications store data the same way: overwrite the current state and move on. A customer changes their address? Update