Operations | Monitoring | ITSM | DevOps | Cloud

There has been a lingering perception that Java applications are slower than applications written in other languages. So, if performance is important for your application, you should not be considering Java as the programming language to use. This perception was true about 20 years ago, when Java was initially used for developing applications. In the early Java implementations, it took a long time for the Java Virtual Machine (JVM) to start.

It has been 25 years since Java came into existence, and it is still one of the preferred platforms among enterprise applications. As technologies evolved, Java's functionality and programming flexibility also matured in parallel, positioning it as a relevant language for over two decades. New memory management systems and garbage collection algorithms are an outstanding example of this evolution.

From AliExpress to Forbes, Starbucks, Instagram, George, Trivago, Uber, and Medium, a vast number of top brands have switched to the PWA environment and recorded a significant rise in their ROI. Especially, in terms of faster app loading & higher customer engagement and retention rate. These brands have not just unveiled the numbers publicly, but have also encouraged others to step into the PWA development world.

In this article we will look at the agent-like instrumentation tool T-Trace. The tool provides non-intrusive instrumentation capabilities for applications running on GraalVM. We will instrument a simple NodeJS application by using T-Trace and OpenTracing API with Jaeger NodeJS tracer.

Working with Java applications has a lot of benefits. Especially when compared to languages like C/C++. In the majority of cases, you get interoperability between operating systems and various environments. You can move your applications from server to server, from operating system to operating system, without major effort or in rare cases with minor changes.

In this tutorial, we will talk about how different Java Garbage Collectors work and what you can expect from them. This will give us the necessary background to start tuning the garbage collection algorithm of your choice. Before going into Java Garbage Collection tuning we need to understand two things. First of all, how garbage collection works in theory and how it works in the system we are going to tune.

When working with Java or any other JVM-based programming language we get certain functionalities for free. One of those functionalities is clearing the memory. If you’ve ever used languages like C/C++ you probably remember functions like malloc, calloc, realloc and free. We needed to take care of the assignment of each byte in memory and take care of releasing the assigned memory when it was no longer needed.