JRush episode 4th: Fresh Java on modern Arm servers

 

Transcript:

Finances for something really useful, not just for hitting the world, which is probably already overheated by global warming. We see that Java moves constantly, and now the frequency and the release schedule have become more regular. We see many exciting things, but the releases are not overloaded, which is good. That’s about Java.

What about me and our company? I have worked at BellSoft for a few years. BellSoft is a unique company because it produces Liberica JDK, the default OpenJDK distribution for Spring Boot containers. It also produces Alpaquita Linux and Alpaquita Native Image Kit, which combine perfectly into the Alpaquita Cloud Native Platform (ACNP). You can learn more about this on our live stream.

I participate in the development of OpenJDK and also speak at events. The overall contribution of our company is very significant in opportunity cases. Before BellSoft, I worked at Oracle in the domain of OpenJDK development, and prior to that, I used to work at Deutsche Bank. So, the topic of financial savings and optimizations is very close to me.

Let’s look at the evolution of mobile phones. This area has developed so rapidly that you wouldn’t be able to capture a device that remains cutting-edge for even half a year. Today, we have devices that are far more modern, powerful, and capable of tasks that were once exclusive to server-class machines. Similarly, in the server domain, new hardware develops rapidly, and the software running on that hardware includes many optimizations. This trend began years ago, and ARM, as both a company and architecture, played a major role. ARM technology has grown enormously, with an estimated 250 billion processors in various devices by the end of last year.

What is an instruction set? It’s a way for software developers to communicate with hardware, telling it what to do to produce valuable results. Instruction sets have multiple versions, with major and minor updates. Among these, the application profile is particularly important for Java developers and users because it allows the JVM to run efficiently with JIT and AOT compilers that optimize runtime performance.

There are also terms like AArch64 or ARM64, denoting execution modes and specific instruction sets for those modes. A single CPU can operate in different modes, with ARM64 also serving as the Linux kernel port for this class of machines. Vendors license ARM technology, develop their hardware, and implement extensions from various specification versions to offer improved performance and features.

Extensions in ARM specifications are often related to cryptography, checksum calculations, and SIMD data processing. For example, the scalable vector extension (SVE) allows efficient computation on long streams of data, such as numerical streams or financial data. Other extensions cater to machine learning tasks. ARM-based servers like ThunderX, with their multi-core designs, demonstrate the scalability and potential of this architecture. While older machines like ThunderX had 96 cores, newer ones boast up to 384 cores, suitable for HPC and server-class workloads.

ARM’s reference designs, like Neoverse, have enabled vendors to implement high-performance hardware. Examples include Apple’s M1 and M2 processors, which exemplify how ARM cores have become increasingly powerful. The latest ARM specifications, such as ARMv9, have already been implemented in both mobile and server-class CPUs. Vendors like Amazon, through their Graviton processors, have consistently improved performance across generations. Amazon reports a 25% performance improvement in their latest generation compared to its predecessor and a tenfold improvement over earlier generations.

In the software ecosystem, ARM has gained significant traction. Most major technologies now target ARM architecture alongside x86. OpenJDK supports ARM natively, enabling optimized performance without emulation. Diagnostic tools for Java, critical for measuring performance and ensuring correctness, have also been adapted for ARM. Performance improvements in OpenJDK 11 and beyond, including intrinsics and optimized functions, further enhance the ecosystem.

Correctness remains a priority, especially for concurrent programs, as ARM hardware is less forgiving of programming errors compared to x86. ARM-based servers now feature hundreds of cores, and racks can support thousands of virtual machines. Amazon’s Graviton processors, for example, offer significant cost savings, leading to rapid growth in ARM computing across clouds.

Development hardware for ARM is now widely available, including Apple Silicon-powered machines and ARM laptops running Linux or Windows. These devices facilitate cross-development for ARM and x86 targets, allowing for multi-cloud deployment and cost-effective solutions. Major cloud providers like Amazon, Oracle, and Azure offer ARM-based instances, ensuring a broad reach for this architecture.

In conclusion, hardware and software advancements on ARM work seamlessly together, offering better performance and lower costs. With the latest Java versions and careful migration strategies, developers can achieve significant benefits. Just remember: correctness is always the responsibility of the programmer. Thank you!

Summary

The video discusses the benefits of using ARM-based hardware for developing and running Java applications. The speaker highlights the significant improvements in performance, cost-effectiveness, and development tools since the first generation of Graviton processors. They also emphasize the importance of software updates and new hardware in achieving improved results.

About Dmitry

Dmitry Chuyko is a Senior Performance Architect at BellSoft, an OpenJDK committer, and a public speaker. Prior to joining BellSoft, Dmitry worked on the Hotspot JVM at Oracle, and before that he had many years of programming experience in Java. He is currently focused on optimizing HotSpot for x86 and ARM, previously being involved in rolling out JEP 386, which enables the creation of the smallest JDK containers.

Social Media

Videos
card image
Feb 6, 2026
Backend Developer Roadmap 2026: What You Need to Know

Backend complexity keeps growing, and frameworks can't keep up. In 2026, knowing React or Django isn't enough. You need fundamentals that hold up when systems break, traffic spikes, or your architecture gets rewritten for the third time.I've been building production systems for 15 years. This roadmap covers three areas that separate people who know frameworks from people who can actually architect backend systems: data, architecture, and infrastructure. This is about how to think, not what tools to install.

Videos
card image
Jan 29, 2026
JDBC Connection Pools in Microservices. Why They Break Down (and What to Do Instead)

In this livestream, Catherine is joined by Rogerio Robetti, the founder of Open J Proxy, to discuss why traditional JDBC connection pools break down when teams migrate to microservices, and what is a more efficient and reliable approach to organizing database access with microservice architecture.

Further watching

Videos
card image
Feb 27, 2026
Spring Developer Roadmap 2026: What You Need to Know

Spring Boot is powerful. But knowing the framework isn’t the same as understanding backend engineering. In this video, I walk through the roadmap I believe matters for a Spring developer in 2026. We start with data. That means real SQL — CTEs, window functions, normalization trade-offs — and understanding what ACID and BASE actually imply for system guarantees. Spring Data JPA is useful, but you still need to know what happens underneath. Then architecture: microservices vs modular monolith, serverless, CQRS, and when HTTP, gRPC, Kafka, or WebSockets make sense. Not as buzzwords — but as design choices with trade-offs. Security and infrastructure follow: OWASP Top 10, AuthN vs AuthZ, encryption in transit and at rest, Docker, Kubernetes, Infrastructure as Code, and observability with Micrometer, OpenTelemetry, and Grafana. This roadmap isn’t about mastering every tool. It’s about knowing what affects reliability in production.

Videos
card image
Feb 18, 2026
Build Typed AI Agents in Java with Embabel

Most Java AI demos stop at prompt loops. That doesn't scale in production. In this video, we integrate Embabel into an existing Spring Boot application and build a multi-step, goal-driven agent for incident triage. Instead of manually orchestrating prompt → tool → prompt cycles, we define typed actions and let the agent plan across deterministic and LLM-powered steps. We parse structured input with Ollama, query MongoDB deterministically, classify risk using explicit thresholds, rank affected implants, generate a constrained root cause hypothesis, and produce a bounded containment plan. LLM handles reasoning. Java enforces rules. This is about controlled AI workflows on the JVM — not prompt glue code.

Videos
card image
Feb 12, 2026
Spring Data MongoDB: From Repositories to Aggregations

Spring Data MongoDB breaks down fast once CRUD meets production—real queries, actual data volumes, analytics. What looks simple at first quickly turns into unreadable repository methods, overfetching, and slow queries. In this video, I walk through building a production-style Spring Boot application using Spring Data MongoDB — starting with basic setup and repositories, then moving into indexing, projections, custom queries, and aggregation pipelines. You'll see how MongoDB's document model changes data design compared to SQL, when embedding helps, and when it becomes a liability. We cover where repository method naming stops scaling, how to use @Query safely, when to switch to MongoTemplate, and how to reduce payload size with projections and DTOs. Finally, we implement real MongoDB aggregations to calculate analytics directly in the database and test everything against a real MongoDB instance using Testcontainers. This is not another MongoDB overview. It's a practical guide to actually using Spring Data MongoDB in production without fighting the database.