Moving Spring Boot microservices from Java 8 to Java 11: what can possibly go wrong?

Day 2 /  / Track 1  /  RU / For practicing engineers

With the new release cycle, the Java platform presents us a new version every six months, but few people in the enterprise world actually switch to it. Java 11, however, became an exception — due to several factors many considered it a good version to move to. It would all be fine and dandy, but if you've got a Spring Boot microservices landscape, the process of the update can become a tiny bit more interesting than simply toggling versions.

In this talk, we'll discuss not only and not so much new language features as general pitfalls of updating Boot microservices, from build (for example, with Gradle) to deployment of Docker containers (for example, in Kubernetes). We'll also talk about what we can expect from moving to Spring Boot 2.1 (which supports Java 11) and its colleagues bringing with them lots of new things and special effects.

Spring Boot microservice apps developers and testers, who are currently moving or planning to move their products to Java 11, might find this talk interesting.

Download presentation
Vladimir Plizga

Since his school days Vladimir was enthusiastic about programming and from then on has managed to code everything: from Soviet programmable calculators to modern CNC tools in production. For the last 8+ years he has been involved in Java backend development of Internet banking at CFT (Center of Financial Technologies). Constantly bothers with ideas about optimization of day-to-day tasks in software development and testing, nurtures solutions for them while jogging or swimming and then puts them into life, experimenting shamelessly on his colleagues. Periodically writes articles and makes talks on Java as well as takes part in organizing SnowOne – Siberian community-driven Java conference.