Why We Bet on Java & Quarkus — and Why .NET Was Never an Option
There is a misconception in the enterprise IT world that refuses to die: that Java is bloated, outdated, and has fallen behind the modern .NET ecosystem. That thinking is firmly rooted in 2014 — the era of Java 8. It is quite possible that influences from the Microsoft consulting world have distorted the view of what Java development actually looks like today.
We made a deliberate choice against the Microsoft stack and for Java with Quarkus. Not out of habit — out of strategic foresight. Here is why.
1. The Cloud-Native Revolution: Quarkus is the Game-Changer
Where traditional Java frameworks once struggled with high memory consumption, Quarkus changed the rules. Through its Supersonic Subatomic Java approach, we achieve boot times in the millisecond range and an extremely low memory footprint.
Efficiency: We pack more workload into the same hardware — whether in Docker, Podman, or Kubernetes.
Developer joy: Live-reloading and first-class cloud integrations make us faster in delivery than classic enterprise teams.
2. Real Cloud Sovereignty (Beyond the Cloud Act)
This is our most important argument: we do not make ourselves hostage to a single ecosystem.
Choosing .NET almost inevitably leads you into the Azure world. But from a GDPR perspective, it is not enough that a server sits physically in Frankfurt if the provider is subject to a US parent company — see the Patriot Act / Cloud Act.
Java is the lingua franca of the cloud world. Our strategy gives us:
- Operation on European cloud providers (e.g. IONOS, OVH, Hetzner)
- Seamless on-premise deployment at the customer's site — Windows, Linux, or macOS
- No vendor lock-in
- And, equally, the option to run on Azure, AWS, or Google Cloud whenever a customer requires it
3. The Reliable Workhorse with Serious Horsepower
Java is not a hype sports car that will be out of fashion next year. It is the dependable estate car with serious torque. While .NET dominates in Azure, Java is often the unchallenged number one — or a very strong second — on AWS, Google Cloud, and in private data centres.
Conclusion: We Build for Reality, Not for Marketing
We value the flexibility to run our applications wherever they are safest and most efficient. With Java and Quarkus, we offer our clients a level of investment security that no proprietary ecosystem can match.
We are not fast and reliable despite Java. We are fast and reliable because of Java. It is time to update the mental image of what Java is.