Language · 1995–now · Object Wave
Java
Write once, run everywhere — then enterprise forever. Still the backbone of serious backend estates.
Why Java stuck
The JVM bought enterprises a stable ABI and a hiring pool measured in millions. Garbage collection and libraries beat rewriting C++ services every budget cycle. Java stuck because banks do not reboot their worldview on Twitter hype.
Case studies
- Lidl walks away from SAP Retail — Estimated €500M+ over seven years before abandonment
- Deutsche Bank absorbs Postbank into integration purgatory — Multi-year, multi-billion IT integration; branch and core systems lagged for a decade
- The ESB hub that became the outage — Hours of nationwide payment and branch downtime; remediation and audit costs in the tens of millions
- Twitter outgrows pure Rails — without declaring Rails dead — Years of JVM/Scala investment alongside Ruby; Fail Whale era ops pain, not a total rewrite bill
- Enterprise blockchain pilots that never left the lab — Eight-figure innovation budgets; production traffic near zero
- AI codebase rewrite pilots that shipped nothing — Six-figure LLM API and SI costs; production cutover: zero
- Low-code to replace engineering — then hire engineers — Seven-figure platform licenses; shadow IT integration debt
Compare with
Related
Framework · 1999–now
J2EE / EE frameworks
EJB-heavy stacks taught a generation that XML config was architecture. Spring and lighter runtimes absorbed the survivors.
Framework · 2003–now
Spring
Java's practical operating system for apps. DI and Boot made enterprise Java shippable again.
Language · 2011–now
Kotlin
Java without the boilerplate ceremony. Google's Android pick and Spring's polite nod kept it climbing.
Language · 2004–now
Scala
JVM language with functional teeth. Spark and Kafka culture kept it relevant long after the Twitter hype cooled.