11 articles tagged architecture.
Bancontact in Belgium, iDEAL in the Netherlands, TWINT in Switzerland — conversion follows familiarity, and a card form is not a neutral default. How we structure Mollie or Stripe so every market pays the way it expects, why asynchronous methods are the part that actually breaks your order flow, and what the cost conversation looks like when someone finally has it.
Roughly seven in ten carts never become an order, and the people who filled them are the warmest audience your shop will ever have. The three-mail sequence we build, the event pipeline that fires it, and why we run it on the same platform that sends your newsletters instead of renting the flow from a US SaaS.
Visitors who use search buy at several times the rate of visitors who browse — which makes the search box a conversion feature, not a technical checkbox. When the database you already run is enough, when typo tolerance pays for itself, and the sync problem that is the real project either way.
Next.js will happily serve your JS bundles from a CDN with one config line. We stopped doing that. Hashed chunks belong to the build that emitted them; images outlive every deploy — and treating both as 'assets' is how a rollback turns into a cache-purge incident.
No database, no admin panel, no plugin updates. Content is MDX in the repo, frontmatter is a Zod schema that fails the build, review is a pull request — and publishing is a merge. The architecture behind this website, and the case where you shouldn't copy it.
React Server Components moved the data question out of the client bundle and into the render. For pages backed by an ERP, that's not a trend to adopt blindly — it's a boundary worth drawing precisely.
Every custom build ships two frontends — the one your customers see and the one only your client's own staff opens. The first earns Next.js. The second is usually paying a tax for machinery it never uses.
Every integration starts with the same question: how do we talk to Odoo? The honest trade-offs between the stock JSON-2 API, community REST modules and a purpose-built gateway — and the one question that picks the right door per consumer.
Storefront, mobile app, carrier webhooks, marketing tools — everything wants to talk to Odoo. Let them all speak JSON-RPC directly and every consumer inherits Odoo's internals. We give them one door instead.
Before a two-developer project grows a Redis, a RabbitMQ and an Elasticsearch, look at what the database you already run can do. SKIP LOCKED queues, tsvector search, LISTEN/NOTIFY — and the measured signals that tell you when to graduate.
Microservices solve an organisational problem, not a technical one. How we decide between a modular monolith and distributed services for custom builds, and the signals that justify the split.