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

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 Bio:
Denis started his software engineering career at Sun Microsystems and Oracle, where he built JVM/JDK and led one of the Java development groups. After learning Java from the inside, he joined the world of distributed systems and databases, where he has remained ever since. His experience spans from the development of database engines and high-performance applications to training and education on the topic of distributed applications.

Parking
Look for Meridian 1 building and park in any unmarked spot in the garage.
There will be multiple signs directing people where to go. I'll be monitoring the comments around the start time to see if people have issues finding the place or getting into the building.