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.