<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Job-Queue on Prima del commit</title><link>https://think.baicode.dev/en/tags/job-queue/</link><description>Recent content in Job-Queue on Prima del commit</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://think.baicode.dev/en/tags/job-queue/index.xml" rel="self" type="application/rss+xml"/><item><title>What Really Needs to Happen Before Responding to the User?</title><link>https://think.baicode.dev/en/blog/what-really-needs-to-happen-before-responding-to-the-user/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://think.baicode.dev/en/blog/what-really-needs-to-happen-before-responding-to-the-user/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s it.&lt;/p&gt;
&lt;h2 id="a-deliberately-simple-architecture"&gt;A deliberately simple architecture&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item></channel></rss>