Talk

Distributed applications - Better off with frameworks, Kubernetes, service meshes or all of them at once?
Conference (INTERMEDIATE level)
Room 5

Software Development based on a distributed (microservice) architecture provides both several advantages and new challenges. In order to take advantage of the distribution it requires implementation of service discovery, routing, load-balancing, resilience mechanisms and more.


Java frameworks like Micronaut, Quarkus or Spring Boot provide dedicated implementations for API Gateways, Service Registries, Circuit Breakers and many more. These functionalities are declared as code dependencies and need to be set at build time.


If the architecture is running on top of Kubernetes there are alternative options to address these problems. So-called service mesh implementations do not have to be part of the actual application code, but can happen on a the network level of the container. A fairly new approach is emerging with the eBPF technology, which claims to enable service meshes with minimal overhead.


With this talk I want to compare the approaches to figure out if one, the other or a combination of them might make sense. The talk is split into a theoretical and a live-demo part.


Matthias Haeussler
Novatec

Matthias Haeussler is Chief Technologist at Novatec Consulting, university lecturer for distributed systems, awarded ambassador of Cloud Foundry and the organizer of the Stuttgart Cloud Foundry Meetup. He advises clients on Cloud strategies and supports implementations and migrations. Prior to that he was employed at IBM R&D Germany for more than 15 years. He has teaching experience from lectures at multiple universities in Stuttgart (DHBW, HSE, HfT). Besides that he is frequent speaker at various national and international conferences and meetups. (e.g. Spring One Platform, Open Source Summit, KubeCon, Voxxed Days, Cloud Foundry Summit, Spring IO, WJAX & more).