Photo: free stock photography (Unsplash licence) — see imprint
The honest minimum
Two application servers behind a load balancer, a managed MySQL, a managed Redis, and object storage for media. That is it. It handles the traffic of most mid-sized B2B shops with room to spare and costs a fraction of a 'cloud-native' redesign.
Where the cloud actually helps B2B
B2B traffic is spiky in a predictable way: Monday morning, month-end, catalogue launch. Being able to double capacity for four hours and pay for four hours is a real advantage — but only if you set it up before the spike, not during it.
Where it burns money
Kubernetes for one shop. A CDN in front of a page that is not cacheable anyway. Multi-region for a company that sells in one country. Every one of these adds a system to operate; none of them adds an order.
Boring beats clever, in production
The best hosting setup is the one your team can debug at 7 a.m. on a Monday when orders are stuck. Simplicity is an availability feature — write the runbook, and prefer the architecture that needs the shortest one.
- Two app servers, managed DB, Redis, object storage.
- Autoscale for known spikes, not for prestige.
- Prefer the architecture with the shortest runbook.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer