Improve your Java apps in containers with Java 13

Have something interesting to share with Java Eastern Europe community?

Become a speaker now

Denys Makogon

Denys Makogon

Principal Member of Technical Stuff at Oracle, Ukraine

Software enthusiast, a fan of designing and developing platform and software as a service application for various cloud infrastructures. He’s a principal software developer, developer advocate at Oracle, concentrating on product development along with bringing well-designed and production-ready integration with cloud solutions, a contributor to various open-source projects, cloud-related technologies along with having fun with IoT devices and photography.

Blogger, photographer, traveler. Denis is a regular attendee and speaker at OpenStack summits (Atlanta, Austin, Paris, Barcelona, Boston) and PyCons (Hong Kong, Singapore, Italy), PyLondinium, Decompile.De. Co-author of OpenStack Application development, OpenStack Trove Essentials.

Speaker's activity

Improve your Java apps in containers with Java 13

Talk

Russian

Java 13 received an improvement to an ACDS (application class-data sharing). JEP 350 stands for improved startup and footprint, extended the existing Class-Data Sharing (“CDS”) feature to allow application classes to be placed in the shared archive. This feature may help to reduce the time needed by JVM to startup your Java code, so, would be very useful for containerized applications (serverless, in particular). Moreover, with some very handful tooling like jdeps and jlink powered-up with Docker multi-stage builds you may significantly improve the way apps being packaged and executed within a container.

In this talk, I’d like to give some practical recommendations on how to build efficient containers for Java applications with Java 13, here’s a few of them:

– why Java 13 is so necessary;
– a purpose of jdeps;
– the purpose of jlink and docker multi-stage.