How Java Apps Litter Beyond the Heap (And What We Can Do About That)

**TAKE A VERY SHORT SURVEY TO HELP SHAPE THE FUTURE OR THE JUG AND HAVE A CHANCE TO WIN ONE OF 50 PASSES TO DEVNEXUS 2023 https://atlj.ug/survey2022**

We will have pizza and drinks before the meetup, and beverages at Taco Mac (nearby) afterward

Abstract
As Java developers, we’re no strangers to the concept of garbage collection. Java apps generate lots of garbage which is meticulously cleaned by CMS, G1, Azul C4, and other types of collectors. However, the story doesn’t end with the Java heap. It only starts there. In fact, your application code constantly generates garbage and triggers collection cycles at the database and even hardware level.

In this session, we take the example of a typical Java application that uses PostgreSQL or YugabyteDB as a relational database and SSDs as a storage medium. From there, we will analyze how our apps litter beyond the boundaries of the Java runtime and what actions we can take to avoid surprises in production.

Speaker - Denis Magda
A little bit about myself. I started at Sun Microsystems and Oracle, where I built JVM/JDK and led one of the Java development groups. After learning Java from the inside, I joined the world of distributed systems and databases, where I have remained ever since. My experience spans from the development of distributed database engines and high-performance applications to training and education on the topic of "Java in the world of databases"

```
```