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.

In this article, we discuss the basics behind Android app development, including architecture, application anatomy, and a quick "Hello, World"app.

Learn how to automate decisions using Quarkus and Kogito.

Java development services have been in use for over 15 years now. Here’s what you need to know about the growth of Java web and mobile application development.

Ever looked for a comprehensive intro to JDBC that is fun and entertaining at the same time? Then look no further than this video tutorial.

In this video tutorial, take a closer look at an introduction and examples on servlets listeners.

Let's see how this feature preview has evolved up to Java 19

Learn how to use the Instancio extension with JUnit 5. Instancio is a Java library that can create and auto-populate test objects.

How is a high-performance, low-latency Java application affected by the JVM version used? Every nanosecond counts for trading and other applications where messages between two different threads are exchanged in about 250 ns! Read this article and find out which JDK variant comes out at the top!

Take a look at how you can use React.js to make a Material-UI in React applications.

In this article, we look at three options for creating Spring Boot projects with Maven and Eclipse: using Spring Initializr, using the STS plugin, and doing it manually.

Due to their asynchronous nature and production complexities, debugging messaging systems has typically been remarkably hard.

In the first part of this series, we take a look at how the design of the web service we'll be creating, and the tech we'll be using to there.

Java constructors of any Java class can be called from the mule configuration XML file using the “New” operation of the Java module.

Discover the importance of developers understanding underlying hardware and learn how some sectors benefit from fast software with predictable latencies.

In the below video tutorial, take a closer look at URL rewriting with demo and Java servlets.

In the below video tutorial, we take a closer look at how to upload/download a file to and from the server.