Event sourcing might be overkill for an e-commerce checkout if your system is small and simple. It's also probably too much if you don't need a detailed history of every single change, or if your team isn't familiar with the pattern. And, if your priority is just getting a basic checkout up and running fast, it adds unneeded complexity.

I've been kicking around the idea of using event sourcing for our e-commerce checkout. We'd basically record every single thing that happens, like when an item hits the cart, or a shipping address gets picked, or payment starts. That'd be amazing for seeing exactly what went down and might even make debugging easier. But, man, dealing with event stores, and projections, and that whole "eventual consistency" thing. It makes me wonder if it's just too much work for something that's mostly just updating stuff and has a pretty clear end goal. Are there specific parts of an e-commerce checkout where event sourcing is a no-brainer, where the good bits totally trump how much harder it is to set up? Or should we just stick with the regular old request-response way for this kind of thing?