JDK 27: G1 as Default GC and Compact Object Headers Proposed
JDK 27 development continues at pace with two JEPs now on track that would change the runtime defaults for all Java applications. The first proposes G1 as the universal default garbage collector, replacing the current situation where different JVM configurations can default to different collectors and creating inconsistent behaviour between development and production environments. G1 has been production-grade since JDK 9, and the proposal acknowledges that making it the official default closes a long-standing gap between what most production deployments actually use and what the JVM selects by default. Teams running ZGC, Shenandoah, or Parallel GC by explicit configuration are unaffected.
The second JEP targets compact object headers as the default layout. Compact headers reduce the header size of Java objects from 16 bytes to 8 bytes on 64-bit JVMs — a change that can reduce heap footprint by 10-20% for workloads with large numbers of small objects, which includes most modern Java applications using collections-heavy data models. The feature has been incubating as an experimental flag for several JDK versions; making it the default signals the JVM team's confidence in its stability. The Vector API meanwhile continues its twelfth incubation cycle, a cadence reflecting ongoing work to align the API with the Project Panama foreign function improvements. Oracle also announced the end of macOS/x64 port maintenance as Apple's transition to Apple Silicon makes the x64 macOS target redundant.
Read more — InfoQ
WildFly Introduces wado: A Rust-Based Container Management CLI
The WildFly team has shipped wado, a new command-line tool written in Rust for managing WildFly server instances in containerised environments. The tool targets the operational gap between WildFly's Java-based management API and the expectations of container-native workflows, where operators typically want lightweight CLI tooling that behaves consistently with Docker and Kubernetes patterns.
wado exposes lifecycle commands (start, stop, restart, deploy, undeploy) through a syntax that maps naturally to container orchestration workflows, and it ships as a single statically-linked binary with no JVM dependency — meaning it can be included in minimal container images or sidecar containers without carrying a Java runtime. For teams running WildFly in Kubernetes, this eliminates the need to exec into containers to run the existing management CLI. The Rust implementation was chosen for memory safety and binary size rather than performance, given that the tool is I/O-bound rather than compute-bound.
Read more — InfoQ
Ecosystem Roundup: Azul/Payara Rebrand, LangChain4j 1.15.0, Google ADK 1.3.0, Micronaut Patches
Azul has rebranded the Payara Platform Community edition into its own product portfolio following its acquisition. The move consolidates Azul's Jakarta EE offering and provides continuity for the significant install base of the Payara Community edition, which will continue under Azul's stewardship.
LangChain4j 1.15.0 is the release most relevant for teams building AI-integrated Java applications. The headline addition is Docling integration — Docling is IBM's open-source document intelligence library that converts PDFs, Word documents, and other formats into structured Markdown optimised for LLM ingestion. With LangChain4j 1.15.0, Java developers building RAG (retrieval-augmented generation) pipelines can now use Docling as a document loader directly from the LangChain4j API, significantly improving the quality of document extraction compared to simple text extraction.
Google ADK (Agent Development Kit) for Java reached 1.3.0 with expanded support for Apigee APIs, giving developers building agents on Google Cloud a route to incorporate API management and gateway capabilities into their agent tool definitions. Micronaut 4.10.14 addresses critical security issues, including an update to Netty 4.2.13 that patches known vulnerabilities in Netty's HTTP parser — any team running Micronaut services exposed to external HTTP traffic should treat this as a priority update.
Read more — InfoQ
Links & Sources
You May Also Enjoy
