By For organizations with legacy Java applications, the biggest hurdle to cloud migration isn’t infrastructure—it’s the code. Years of business logic buried in monolithic apps make modernization feel like a risky rewrite. But Azul’s SVP of Corporate Development and Partner Alliances, George Gould, says it doesn’t have to be that way.
“At Azul, every JVM we ship is TCK tested,” says Gould, referring to the rigorous Technology Compatibility Kit used to ensure JVM compliance with Java specifications. “That’s over 100,000 unit tests per build.” This compatibility layer is what enables Java’s long-touted mantra: write once, run anywhere.
📹 Going on record for 2026? We're recording the TFiR Prediction Series through mid-February. If you have a bold take on where AI Infrastructure, Cloud Native, or Enterprise IT is heading—we want to hear it. [Reserve your slot
That “anywhere” now includes cloud and Kubernetes environments, thanks to the integration of Azul’s JVMs into the Qube offering by Payara. Developers can choose between Azul Platform Core—a well-supported and secure JDK for general use—or the high-performance Platform Prime, which includes the Zing JVM.
Gould explains the advantage: “With Zing, you get better metrics, higher throughput, faster compilation—flat-out better performance.” This is especially useful for latency-sensitive or high-throughput applications like e-commerce, trading, or ad tech platforms.
The real breakthrough, however, is that none of this requires touching the original code. “You didn’t change a line of code,” says Gould. That’s a game-changer for the 40% of enterprise Java apps still running on-premises. It removes the top objection: that migration is too risky or resource-intensive.
“You can always refactor later,” he adds. “But it no longer becomes a barrier to moving to the cloud in the first place.”
This partnership isn’t just between Azul and Payara. It includes hardened container providers like Chainguard and RapidFort, ensuring that security and container hygiene are also baked into the process.
The result is a low-friction, high-trust migration path for legacy Java apps—with improved KPIs or lower infrastructure costs waiting on the other side. Whether you’re focused on performance, cost containment, or simply unblocking innovation, this is a compelling route forward.
