What to Expect from Java 13: New Features Explained

Java has long been one of the most widely used programming languages in the IT world. It is a versatile language that supports a wide variety of applications, from small applications running on a single machine to large-scale distributed systems. With its vast ecosystem, robust libraries, and cross-platform capabilities, Java continues to be a top choice for developers around the world.

Recently, a new version of Java was released: Java 13. Every new release of Java comes with improvements, bug fixes, and new features, and Java 13 is no exception. Developers and enthusiasts alike are always curious about the new capabilities introduced in the latest versions. Java 13 has garnered attention for the enhancements it brings to the table, some of which were eagerly awaited by developers working in various domains of software development.

One of the major changes with Java 13 is the shift to a six-month release cycle for Java updates. This new release cycle aims to provide a more consistent and faster stream of updates for developers. The frequent updates allow for quicker adoption of new features and improvements. This shorter release cycle means that developers can expect more incremental changes, rather than waiting for large updates to introduce major changes.

In this article, we will look in-depth at some of the most notable features introduced in Java 13. From the inclusion of text blocks to the reimplementation of legacy APIs, Java 13 offers several improvements aimed at making development easier and more efficient. Let’s dive into some of the key features of this latest release.

Text Blocks in Java 13

One of the most significant additions to Java 13 is the introduction of text blocks. Text blocks are multi-line string literals that help developers avoid the common issue of escape characters in strings. Before Java 13, strings in Java often required developers to use escape sequences to format special characters, such as newlines or tabs, when working with strings that span multiple lines. This not only made the code more difficult to read but also led to errors and issues when formatting strings.

Text blocks aim to simplify this process. They allow developers to write multi-line strings in a natural and readable way. With this feature, developers no longer have to manually add escape sequences like \ n or t when writing strings that span multiple lines. Instead, text blocks allow you to define a string over multiple lines, maintaining the readability and structure of the code.

Benefits of Text Blocks

The introduction of text blocks brings several key benefits to Java development:

1. Improved Readability: Text blocks make it easier to format and read multi-line strings. This is particularly useful when dealing with JSON data, SQL queries, or even long messages that span multiple lines. 
2. Automatic Formatting: One of the most appealing aspects of text blocks is that they can automatically format strings, making the code more consistent and easier to maintain. Developers no longer need to worry about manually formatting each line of a string. 
3. Ease of Use: Text blocks are easy to implement, and their syntax is straightforward. The string is enclosed within triple quotes, and it can span multiple lines without requiring additional escape sequences. 
4. Support for Non-Java Code: Text blocks also improve the readability of strings that represent code written in non-Java languages. For example, it’s now easier to write SQL or JSON code directly in Java, without having to worry about escape characters. 

These benefits make text blocks an excellent addition to Java 13, and they are expected to significantly improve how developers handle strings in their programs.

Legacy Socket API Reimplementation

Another important update in Java 13 is the reimplementation of the legacy socket API. Java’s socket API provides a way for programs to communicate over networks, enabling the creation of networked applications. While Java’s java.net.Socket and java.net.ServerSocket classes have been reliable for many years, they have also become somewhat outdated.

The reimplementation of the legacy socket API in Java 13 is a step toward improving the simplicity and complexity of networking code. The new implementation offers a more modern approach to working with sockets while retaining the simplicity that Java developers expect. The goal is to make it easier to maintain and debug networking code while providing better performance and functionality.

The new implementation also works well with fibers, which are user-mode threads. Fibers are a lightweight alternative to traditional threads, offering better performance in certain scenarios. By adapting the socket API to work with fibers, Java 13 ensures that developers can take advantage of the latest advancements in threading and concurrency.

Switch Expression Enhancement

Java 13 also brings an enhancement to the switch expression, a feature that was introduced in Java 12. Switch expressions were designed to improve the flexibility and readability of the switch statement. They allow developers to use the switch statement as both a control flow statement and an expression, making the code more concise and easier to understand.

One of the key changes in Java 13 is the replacement of the break statement with yield. In previous versions of Java, the break statement was used to exit a case in the switch statement. However, in Java 13, the yield statement has been introduced to return a value from a case in the switch expression.

The enhancement is aimed at making switch expressions more powerful and flexible. Developers can now use switch expressions to return values in a more consistent way. Additionally, Java 13 allows for both fall-through and no fall-through behavior in switch expressions, depending on how the case labels are written.

Why is this important?

The switch expression is important because it simplifies the use of conditional logic in Java. Before Java 12, the switch statement was a more cumbersome control flow construct, and developers had to rely on workarounds to return values or perform complex logic within a switch block. With the switch expression in Java 13, developers can now write cleaner and more concise code.

Performance Improvements and Garbage Collection Enhancements in Java 13

In the previous section, we explored the major new features in Java 13, including text blocks, the reimplementation of the legacy socket API, and improvements to the switch expression. Now, let’s dive into some of the performance-related enhancements introduced in Java 13, particularly focusing on the Z Garbage Collector (ZGC) improvement and the extension of Application Class Data Sharing (AppCDS). These features aim to further optimize Java’s efficiency, memory management, and overall performance, helping developers build even more scalable applications.

Z Garbage Collector Enhancement

Garbage collection is a crucial aspect of any programming language, and Java is no exception. Java has had several garbage collectors over the years, and in Java 11, the Z Garbage Collector (ZGC) was introduced as an experimental feature. ZGC was designed to offer low-latency garbage collection with high scalability. This made it a great choice for applications that require minimal pause times and handle large amounts of memory.

However, the ZGC in Java 12 and Java 13 received significant improvements, one of the most notable being the ability to return unused memory to the operating system. In earlier versions of ZGC (such as in Java 12), while the garbage collector could manage memory more efficiently, it did not return unused memory to the operating system, which sometimes led to memory stagnation. This could cause performance issues when applications experienced long periods of low memory usage, as the unused memory was retained and not reclaimed.

With the Java 13 update, ZGC has been enhanced to allow unused memory to be returned to the operating system. This is a significant improvement because it reduces memory pressure, especially in scenarios where an application experiences fluctuating memory usage. By freeing up unused memory, the operating system can use it for other processes, thus improving overall system performance and ensuring that memory is not unnecessarily locked up.

Why This Matters

The ability to return unused memory is particularly useful for long-running applications or those that operate in environments with heavy resource contention, such as cloud-based applications or microservices. By returning unused memory to the operating system, Java 13 ensures that memory is managed more effectively, leading to better resource utilization.

This enhancement to the ZGC also contributes to the overall low-latency characteristics of the garbage collector, making it suitable for applications that require predictable performance, such as real-time systems or large-scale enterprise applications.

Application Class Data Sharing (AppCDS) Extension

Another significant feature in Java 13 is the extension of Application Class Data Sharing (AppCDS). AppCDS is a mechanism that allows Java applications to share class data across different JVM instances. This feature was initially introduced in Java 5, but it was further improved in Java 12 to enhance startup performance and reduce memory consumption.

In Java 13, AppCDS has been extended to enable the archiving of classes when the application implementation ends. This extension allows classes that were loaded during the application’s execution to be archived and reused later. This results in faster application startup times since the JVM can load the pre-archived classes instead of loading them from scratch each time the application runs.

AppCDS works by sharing class data across JVM instances, which helps reduce memory usage. The shared data is stored in a special archive file, which can be reused across multiple instances of the same application or different applications running on the same machine. This reduces the need to load the same class data multiple times, resulting in significant memory savings.

Benefits of AppCDS

The extension of AppCDS in Java 13 brings several key advantages:

1. Reduced Startup Time: By archiving classes at the end of an application’s execution and reusing them, Java 13 reduces the time required for the JVM to load classes during the startup process. This is especially helpful for applications that are started frequently, such as microservices in cloud-based environments. 
2. Improved Memory Efficiency: The use of shared class data between different JVM instances reduces the overall memory consumption of an application. Instead of each instance having its copy of the class data, the data can be shared, making better use of available system resources. 
3. Faster Application Restarts: With AppCDS, applications that need to restart often can benefit from faster restarts, as the JVM does not need to reload class data each time the application starts. 

This extension to AppCDS makes it an even more valuable tool for optimizing application performance, particularly for cloud-native applications or services running in containers, where rapid scaling and fast restarts are often crucial.

Additional Features and Performance Improvements

In addition to the ZGC and AppCDS enhancements, Java 13 introduces several other performance-related improvements that contribute to the language’s overall efficiency. These include:

The default Native GSS API Library on Windows

Java 13 includes a new feature for Windows users: the addition of a default native GSS API library. The Generic Security Services (GSS) API is commonly used for providing authentication services and secure communication. With this new default library, Windows users no longer need to rely on third-party libraries or implement custom solutions for GSS-based services. This simplifies development and improves consistency across different platforms.

Canonical XML 1.1 URI Sequence Constants

Java 13 introduces new sequence constants for Canonical XML 1.1 URI. This is a specialized feature aimed at developers working with XML processing, particularly when dealing with Canonical XML (C14N) serialization and deserialization. By providing these constants, Java makes it easier for developers to work with XML data and ensures that URI sequences are handled correctly and efficiently.

Configurable Read Timeout for CRLs

Another small but useful improvement is the ability to configure the read timeout for Certificate Revocation Lists (CRLs). CRLs are essential for ensuring that digital certificates are still valid and have not been revoked. With the new configurable read timeout feature, developers can customize how long the system will wait before timing out when retrieving CRLs. This is particularly useful in environments with slow network connections or when working with large CRL datasets.

MS-CNG (Cryptography Next Generation) Support

Java 13 also adds support for MS-CNG (Microsoft Cryptography Next Generation), a cryptographic API that is used in newer versions of Windows. With this addition, Java developers can more easily integrate cryptographic services on Windows systems, providing better security and compliance with modern cryptographic standards.

Security and JVM Updates in Java 13

In the previous section, we explored some of the key performance improvements in Java 13, including the enhancements to the Z Garbage Collector, the extension of Application Class Data Sharing (AppCDS), and several other performance optimizations. Now, let’s turn our attention to some of the critical security and Java Virtual Machine (JVM) updates introduced in Java 13. These updates ensure that Java remains secure, reliable, and effective for developers working on modern software projects.

Security Updates in Java 13

Java, being one of the most widely used programming languages in the world, places a high priority on security. With every release, Java incorporates fixes for known security vulnerabilities and introduces new features to enhance the language’s overall security posture. Java 13 is no different, and it brings a range of security updates that help developers maintain secure applications and systems.

Support for Kerberos Cross-Realm Referrals

One of the notable security enhancements in Java 13 is the addition of support for Kerberos cross-realm referrals. Kerberos is a network authentication protocol that is widely used for secure communication over untrusted networks. It works by using cryptographic tickets to authenticate users and services, providing a secure method for verifying identities without transmitting passwords over the network.

In Java 13, the support for Kerberos cross-realm referrals has been extended, making it easier to configure Kerberos authentication across multiple realms. This improvement allows systems that are part of different domains or administrative zones to authenticate users and services seamlessly, enhancing interoperability in complex network environments.

Cross-realm referrals are particularly useful in large, distributed systems where services and users may reside in different security domains. This addition makes Java 13 a more robust choice for enterprise environments that require secure cross-realm authentication.

Resumption of Sessions Without Server-Side State in JJSE

Another security-related feature in Java 13 is the ability to resume sessions without the need for server-side state in Java Secure Sockets Extension (JSSE). In previous versions of Java, when a session was resumed over SSL/TLS, the server had to maintain state information for the session, which could be resource-intensive.

With the new approach introduced in Java 13, Java allows for session resumption without relying on server-side state. This feature reduces the burden on servers by eliminating the need to store session state information. It improves both scalability and performance while maintaining secure connections between clients and servers. This is particularly useful in environments where high-performance and high-availability are required.

Other Security Enhancements

In addition to the Kerberos and session resumption features, Java 13 also includes several other smaller security improvements, such as the introduction of additional cryptographic algorithms, enhancements to the Secure Random API, and improvements to the Java Cryptography Architecture (JCA). These updates ensure that Java applications remain secure by supporting the latest standards in cryptography and network security.

Java’s commitment to maintaining a robust security framework is evident in its ongoing security updates. With each release, developers can be confident that Java is up-to-date with the latest security protocols, ensuring that their applications remain protected against emerging threats.

JVM Updates in Java 13

Java’s JVM (Java Virtual Machine) is the cornerstone of its platform, responsible for executing Java bytecode and ensuring the portability of Java applications across different platforms. With each new version of Java, there are updates to the JVM that improve its performance, stability, and feature set. Java 13 continues this tradition with several notable changes to the JVM.

JVM Support for MS-CNG

As mentioned in the previous section, Java 13 introduces support for the Microsoft Cryptography Next Generation (MS-CNG) API on Windows. This update allows Java applications running on Windows to take advantage of the platform’s native cryptographic services. MS-CNG is a modern cryptographic API that supports the latest encryption algorithms and security standards.

By integrating MS-CNG support into the JVM, Java 13 provides developers with a more seamless experience when building secure applications on Windows. This integration ensures that Java developers can access the full range of cryptographic functions provided by the Windows operating system without relying on third-party libraries or custom implementations.

JVM Performance Improvements

Java 13 also brings several performance optimizations to the JVM itself. These improvements aim to reduce memory usage, improve garbage collection, and ensure that Java applications run more efficiently.

For instance, the JVM has received optimizations to reduce memory footprint and improve the way it handles large datasets. These changes are particularly beneficial for applications that process large amounts of data, such as big data platforms or data processing systems. By improving memory management, Java 13 ensures that applications can handle larger workloads without running into memory-related issues.

Additionally, there have been improvements to the JVM’s Just-In-Time (JIT) compiler, which compiles Java bytecode into machine code during runtime. These optimizations result in faster application startup times and more efficient execution of Java programs.

New Sequence Constants for Canonical XML 1.1 URI

Java 13 also introduces new sequence constants for Canonical XML 1.1 URI. Canonical XML is a standard for XML serialization that ensures consistent representation of XML data, regardless of formatting differences like whitespace. This update provides constants for handling URI sequences in Canonical XML 1.1, making it easier for developers to work with XML data and ensuring that URIs are handled correctly and efficiently.

This update improves Java’s support for XML processing, which is crucial for many enterprise applications that rely on XML for data exchange and configuration. By providing the necessary constants for working with Canonical XML, Java 13 simplifies the process of handling XML data and reduces the potential for errors in XML parsing and processing.

The Impact of JVM Updates

The JVM updates in Java 13 have a direct impact on the overall performance and reliability of Java applications. By improving memory management, enhancing cryptographic support, and optimizing execution efficiency, Java 13 continues to provide developers with the tools they need to build high-performance, secure applications.

For enterprise developers, these improvements are particularly valuable. Java is often used for large-scale applications, including web servers, enterprise resource planning (ERP) systems, and big data platforms. The JVM updates in Java 13 make it easier to scale these applications, optimize their performance, and ensure that they run efficiently even under heavy loads.

Other Enhancements and Tool Improvements in Java 13

In the previous parts of this article, we have explored the core features and improvements introduced in Java 13, including text blocks, performance enhancements such as the Z Garbage Collector and AppCDS extension, as well as security and JVM updates. Java 13 also includes several other smaller, yet impactful improvements aimed at enhancing the developer experience, debugging capabilities, and making the Java ecosystem more efficient overall. In this section, we will look at these additional features that make Java 13 an even more powerful and user-friendly platform for developers.

Additional Default Native GSS API Library on Windows

One of the notable updates in Java 13 is the inclusion of an additional default native Generic Security Services (GSS) API library for Windows users. The GSS API is used to provide authentication and secure communication between clients and services in a networked environment. Java 13 now includes a default native implementation of the GSS API for Windows, which simplifies the process of integrating Java applications with Windows-based security services.

Previously, developers had to rely on third-party libraries or custom implementations to integrate GSS functionality into their Java applications on Windows. This new feature eliminates the need for additional dependencies, making it easier for developers to work with secure network communication in Java on Windows systems.

The addition of the default GSS API library improves the overall consistency and reliability of security services on Windows. It also streamlines development for developers who need to implement secure communication, such as Single Sign-On (SSO) or other Kerberos-based authentication protocols, without having to manage external dependencies.

Configurable Read Timeout for Certificate Revocation Lists (CRLs)

Another valuable feature introduced in Java 13 is the ability to configure the read timeout for Certificate Revocation Lists (CRLs). CRLs are crucial for ensuring that digital certificates are valid and have not been revoked. When dealing with secure communications, applications need to check whether a certificate has been revoked by the issuer. In the past, Java’s default timeout for reading CRLs was fixed, and developers had limited control over how long the system would wait before timing out during the CRL retrieval process.

Java 13 addresses this limitation by allowing developers to configure the read timeout for CRLs. This enhancement is particularly useful in environments where network latency or slow connections might lead to long CRL retrieval times. By providing flexibility in how long the system will wait to read CRLs, developers can ensure that their applications are more resilient and can handle varying network conditions without causing unnecessary delays or timeouts.

Support for MS-CNG (Microsoft Cryptography Next Generation)

Java 13 also introduces support for Microsoft’s Cryptography Next Generation (MS-CNG) API. MS-CNG is a modern cryptographic API used in newer versions of Windows, and it provides support for a wide range of cryptographic algorithms and secure communication protocols. With this addition, Java developers can now leverage the full range of cryptographic functions available on Windows systems.

The integration of MS-CNG into Java 13 ensures that developers can easily access and use the latest cryptographic standards on Windows without relying on third-party libraries or custom solutions. This addition improves Java’s ability to work with modern cryptographic systems and enhances the overall security of applications running on Windows.

Resumption of Session Without Server-Side State in Java Secure Sockets Extension (JSSE)

Java 13 introduces a significant improvement to the Java Secure Sockets Extension (JSSE) by allowing the resumption of sessions without the need for server-side state. JSSE is a set of APIs used for implementing secure communication over networks, such as SSL/TLS protocols. In previous versions of Java, when a session was resumed over SSL/TLS, the server needed to maintain state information for the session. This could become a performance bottleneck in high-traffic environments, as storing session information on the server side requires additional resources.

In Java 13, session resumption has been optimized to eliminate the need for server-side state. This improvement enhances scalability and reduces the memory overhead on servers by not requiring them to store session information for every SSL/TLS session. It also speeds up the process of resuming sessions, providing a better user experience in environments where secure connections are frequently established and terminated.

This improvement is particularly beneficial for environments that require high performance and low latency, such as web servers and cloud-based applications. By reducing the load on the server and speeding up session resumption, Java 13 helps ensure that applications can scale effectively while maintaining secure communications.

New Sequence Constants for Canonical XML 1.1 URI

For developers working with XML data, Java 13 introduces new sequence constants for Canonical XML 1.1 URI. Canonical XML is a method of representing XML data in a standardized format, ensuring that XML documents are consistently serialized despite differences in whitespace or formatting. This new addition helps developers work with URI sequences in the context of Canonical XML 1.1 more effectively.

By providing these sequence constants, Java 13 simplifies the process of handling URIs in XML documents, reducing the potential for errors and improving consistency in XML processing. This is particularly useful for applications that rely on XML data interchange, such as web services or enterprise integration systems.

Debugging and Developer Tools Improvements

Java 13 also brings several improvements to debugging and developer tools, making it easier for developers to troubleshoot and optimize their applications. These tools include better support for remote debugging, improved performance monitoring, and enhanced diagnostics capabilities.

For example, Java 13 introduces better integration with modern development environments, enabling more seamless debugging of distributed applications. The ability to remotely debug applications running in production environments is a crucial feature for developers working with microservices, cloud platforms, and other distributed systems.

Additionally, Java 13 provides new diagnostic tools that allow developers to analyze the performance of their applications more effectively. These tools provide valuable insights into memory usage, CPU performance, and garbage collection behavior, helping developers identify bottlenecks and optimize their applications for better performance.

Excluded Features in Java 13

While Java 13 introduces a variety of exciting new features, it is important to note that some features from previous versions of Java have been excluded or deprecated. These exclusions include the removal of certain system properties, changes to the handling of runtime trace methods, and the discontinuation of support for specific cryptographic certificates.

For example, Java 13 removes the AWS Toolkit system property, which was previously used for AWS-specific configurations. This change is part of an ongoing effort to streamline Java’s core functionality and remove unnecessary dependencies. Similarly, some VM options and certificates related to specific cryptographic standards have been removed from the Java 13 release.

While these exclusions may require developers to update their applications, they are part of Java’s ongoing evolution to improve performance, security, and maintainability. Developers should review the changes and ensure that their applications are compliant with the latest version of Java.

Conclusion 

Java 13 brings a host of new features and improvements that enhance the developer experience, security, and performance of Java applications. From the addition of the default GSS API library on Windows to the improvements in session resumption and XML processing, Java 13 introduces several important updates that make the language even more powerful and versatile.

The continued focus on performance optimization, security enhancements, and developer tools ensures that Java remains a top choice for building modern, scalable, and secure applications. As always, Java’s evolution continues, and developers can look forward to more exciting updates in future releases.

With the six-month release cycle now in effect, Java 13 is just one step in an ongoing journey to make the language more efficient, secure, and developer-friendly. By keeping up with the latest releases and embracing the new features introduced in Java 13, developers can ensure that their applications are not only up to date but also optimized for performance, security, and scalability.