21 articles tagged architecture.
The fix took forty minutes and a quarter of your users still hit the bug three weeks later, because a mobile release is a copy on somebody else's device. What over-the-air updates genuinely replace, the minimum-version gate you have to ship in v1 or never, why your API is permanently multi-version, and the autumn maintenance window nobody schedules.
Every self-hosted tool ships its own user table, and a leaver has to be removed from all of them. The identity provider we put in front of Grafana, Metabase, ArgoCD and the custom apps — which parts map cleanly, why Odoo is the awkward one, and what you owe the thing once everything depends on it.
A rename is the cheapest thing a database does and one of the most dangerous things a deploy does, because two versions of your application are always live at once. Expand, backfill, contract — the release boundary that makes it safe, the locks that bite anyway, and what changes when Odoo owns the schema.
Postgres can push an event to your app the moment a row commits. The trigger that catches every writer including the ERP, the listener that survives a reconnect without losing a change, the pooler that silently breaks all of it, and the bulk import that turns a live board into 40,000 notifications.
A dark screen is a support ticket. A screen still showing last week's price is a lie in your store, and nothing in a normal monitoring stack will tell you about it. Content as a versioned bundle instead of a URL, day-parts that depend on a clock you don't control, expiry as a safety feature, and telemetry that reports what's actually on the glass.
Three good answers to "we need a website", each right for a different shape of requirements. The five questions that actually decide it — who edits, what it talks to, whether visitors change state, who owns it in three years, and what the risk surface has to look like — plus the two migrations that go wrong in both directions.
In an internal tool, the same order is on screen in five places at once, and every mutation has to remember all five. What a client-side store fixes that a cache can't — collections, live queries, optimistic writes that roll back on their own, and the working set that has to fit in a browser.
A reminder tells the customer something. A confirmation tells your calendar something — and only one of those lets you refill the slot. The virtual number that makes replies possible, the matching problem nobody warns you about, parsing what people actually type in three languages, and the Odoo automations that reschedule without a human.
SIM-swap risk is real; so is the customer who will never install an authenticator app. An honest matrix of SMS OTP against TOTP and passkeys — plus the attack that shows up on your invoice instead of your incident channel, the network APIs that turn a phone number back into a useful signal, and why the recovery path decides your real security level, not the login screen.
One shared sending platform means your invoice inherits your campaign's spam score — but reputation is only the argument people already know. The queue that starves password resets behind 80,000 newsletters, the suppression list that must never be shared, and the consent boundary a platform should enforce rather than trust you to remember.
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.