Ideas on sovereign, business-driven technology
Practical thinking on enterprise architecture, EU data sovereignty, Kubernetes, and compliant automation — from the work we do every day.
Why change should be business-driven, not IT-led
Every system, tool, or purchase should answer a business requirement — not land because someone thought it was clever. When the business drives change, you stop shipping things nobody asked for.
Read moreEU digital sovereignty: what it actually means for your cloud
Sovereignty is not a checkbox or a data-centre location. It is about who can compel access to your data — and designing so the answer stays in Europe.
Read moreOne cluster per solution wastes what Kubernetes gives you
Kubernetes strips the operating-system overhead from every app, and for stateless workloads the disks and backups too. Run a cluster per solution and per environment, though, and you throw away its biggest win.
Read moreKnow every application you run — or pay for it twice
If you can't list the applications you run, you can't know which capabilities you already have — and you end up buying the same one twice. Keep the catalogue where your service management lives.
Read moreThe roles that keep a delivery team shipping
With many developers, clear roles are what keep delivery predictable: a product owner close to the business, two kinds of project manager, and a spec that's settled before it reaches the team.
Read more