Java Web Development (JSP/Servlets) Services

Here’s today’s invitation: join the GitHub Copilot CLI Challenge and build something with Copilot right in your terminal. Visit the challenge page for the rules, FAQ, and submission template.

Why I’m Excited About Copilot CLI (especially for Java)

If you write Java for a living, you already know the truth: the terminal is where we build and test. It’s where feedback loops are short and where most productivity gains come from “small wins” repeated hundreds of times.

So, what does a file system mean to you? Most think of file systems as directories and files accessed via your computer: local disk, remotely shared via NFS or SMB, thumb drives, something else. Sufficient for those who require basic file access, nothing more, nothing less.

That perspective on file systems is too limited: VCS repositories, archive files (zip/jar), and remote systems can be treated as file systems, potentially accessed via the same APIs used for local file access while still meeting security and data requirements. Or how about a file system that automatically transcodes videos to different formats or extracts audio metadata for vector searches? Wouldn’t it be cool to use standard APIs rather than create something customized? Definitely!

Every major Jakarta EE release tends to have a defining theme. Jakarta EE 11 was about modernization: a new baseline with Java 17, forward compatibility with Java 21, and a decisive cleanup of long-standing technical debt. Jakarta EE 12 builds directly on that momentum, but its direction is different. This release is less about removing the past and more about aligning the future.

Jakarta EE 12 is best understood as the Data Age of enterprise Java.

Enterprise Java persistence has never really been about APIs. It has always been about assumptions. Long before frameworks, annotations, or repositories entered the picture, the enterprise Java ecosystem was shaped by a single, dominant belief: persistence meant relational databases. That assumption influenced how applications were designed, how teams reasoned about data, and how the Java platform itself evolved.

This article is inspired by a presentation given by Arjan Tijms, director of OmniFish, titled “Next-level persistence in Jakarta EE: Jakarta Data and Jakarta NoSQL.” Delivered in 2024, the talk offers a clear and pragmatic view of why Jakarta EE persistence needed to evolve, how Jakarta Data fits into the platform, and how it relates to Jakarta Persistence and Jakarta NoSQL. While the presentation provides the technical backbone, this article expands on the historical context and architectural motivations behind that evolution.

Java has become one of the world’s most versatile programming languages, chosen for its adaptability, stability, and platform independence. Its extensive ecosystem encompasses virtually every application type, from web development to enterprise solutions, game design, the Internet of Things (IoT), and beyond.

With an estimated 51 billion active Java Virtual Machines (JVMs) globally, it goes without question that Java powers a substantial portion of modern software infrastructure.