Job-Queue
What Really Needs to Happen Before Responding to the User?
A few years ago my brother-in-law asked me to build a small e-commerce site. The idea was simple: sell online the artisanal digestive liqueur he made. A handful of products, a bare-bones checkout, the receipt printed and slipped straight into the package.
That’s it.
A deliberately simple architecture
At that point there was no reason to complicate the architecture. Every request started and ended in the same place: the user confirmed the order, the application completed every operation, the response came back immediately.