In this post, we take a look at Metaspace, and explain how to increase the performance of your JVM with a few simple commands.

Microservices are replacing monoliths every day. So, let's explore how Java devs can put them to work with the help of their favorite frameworks.

A curious case of switching to Java from Kotlin.

Insecure deserialization is a common and dangerous web application security threat. Boost your threat profile by incorporating a JID Detection API.

This tutorial shares a simple example of deploying a Java application to Elastic Beanstalk by using Amazon CDK.

With the client+server RIA platform concept of GraniteDS, applications can be written faster with less code, have a clean architecture, and separated layers.

The two technologies are very similar, so what are the differences?

This article illustrates how to create a standing up reminder using sample code, to help break the bad habit of sitting too long.

Detailed Comparison Between Kotlin and Java! Here you will know which will be the best for your project.

Learn how to modify Java command-line arguments. Java command-line arguments enable programmers to pass the arguments during the execution of the program.

In this post, let’s learn a little more about C1 and C2 compiler threads and how to address their high CPU consumption.

Do you want to know more about WebSockets? Here you will find some more information about them and learn how to create a simple chat application.

This article will cover more about the next steps of Jakarta EE around the world of data and its techniques to work as more besides just the data source.

In this post, learn how to follow security policies while developing applications for the cloud by using Kubernetes Secrets.

In this fourth article of the ultra-fast series, learn a new database that can make your microservices scale up quickly in the Java world!

A look at the garbage Java apps generate, demonstrated with some help from Postgres and SSDs.

This article will present an overview of how Java has grown into today's complex system and why it continues to remain a contemporary development environment.

Introduction to KEDA—event-driven autoscaler for Kubernetes, Apache Camel, and ActiveMQ Artimis—and how to use it to scale a Java microservice on Kubernetes.

Your one-stop-shop for all things authentication and authorization.

Some have probably been expecting it for a long time, and this week it finally happened. Apache Harmony, an open source cleanroom implementation of Java was moved to the Apache Attic, where inactive projects are sent. The project management committee voted 20 to 2 in favor of discontinuing the project. One of the votes against moving Harmony to the Attic was PMC chair Tim Ellison, who thought it was too early to deactivate Harmony. But Harmony was probably already dead and buried once it's primary corporate sponsor, IBM, switched its support to OpenJDK last year. Android has not gotten invovled in the Harmony project recently because of their ongoing lawsuit with Oracle. Developers may still use the code while it resides, inactive, in the Apache Attic. Here were some comments from last year when most predicted the death of Harmony: "Well, pragmatically I would prefer one great open source JVM, rather than multiple average ones. So as long as OpenJDK is still GPL, I see no reason to cry over this. Reality is that I don't know of a single project going into production using Harmony. " --Jacek Furmankiewicz "Google has single handedly turned around the disaster that was J2ME. Assuming they'll eventually sort out the patent mess (and given the stakes, they will) that removes from the equation all the partners that had very little to bring to the table when it comes to mobile Java. Meanwhile, Oracle and IBM need to demonstrate through actual technical innovation that they are still relevant in the Java world. Last time I checked, the enterprise Java world was dominated by things like Spring (under the Apache license) rather than any JCP efforts. Oracle bought an empty shell. Filing patent related lawsuits left and right is probably not going to be very helpful since that tends to scare away customers. So, I'm hoping that this will end pretty quickly. Once it does, all parties can get back to moving the agenda forward on the run-time, language, and APIs. There is a lot of stuff that needs to start happening there and if Oracle won't do it, others will do it for them. In a nutshell, that's why Google is shipping Harmony rather than CDC. I'm pretty sure Google would have preferred to stay in the Sun community a few years ago if only Sun was not being so unreasonable." --Jilles van Gurp "For me, the question is: what to we, as coder, expect from Java? I don't think I will ever use a self patched SDK/openSDK in any production; I even doubt I would ever work in a project which would like todo that. Oracle might be the bad boy here, but -man!- they know techology. I strongly believe, that the SDK will be less stagnant in performance/features and lots of those 10 year old problems in Bugzilla will finally be tackled. Sun let the "open" part of Java start smelling and people started to invest significant time in non-Java languages like Scala and new ways of dealing with partitioning of services aka OSGi containers. Since JVM 1.5 they were not really able to focus this community power to anything bigger then some lame syntactic sugar and a DOA flash clone. Harmony is a nice place to play around with an open JVM, but I think this job moves more over to the more general LLVM. And I don't think that I want to bet my (professional) future on the fact that Google has to step always in when the rest of the industry has just a bad haircut day. IBMs move is logical. Whatever Harmony is or was, the impact was already limited. You simply can't build such infrastructure without more people building it. One company alone wouldn't push Apache or Tomcat, and any serious openJDK shouldn't do either." --Igor Laera Let the conversation now continue.