Distributed Apps & Kubernetes: Better off with frameworks, service meshes or both | Haeussler (EN)

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 the 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 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.

➜ Abonniere JAVAPRO und verpasse keine News:

---- Über uns: ----

JAVAPRO ist das Magazin für professionelle Java-Entwicklung in der Praxis.
Über das Magazin hinaus ist JAVAPRO Veranstalter der jährlich stattfindenden Entwickler-Konferenz JCON. Auf der JCON stehen Core Java, Enterprise Java, Microservices, APIs und Frameworks im Fokus.
Auf diesem Kanal finden sich Interviews, Sessions, Tipps & Tricks und alles, was das (Java)-Entwickler-Herz begehrt.

➜ Jetzt kostenlos Magazin anfordern:

---- Folge uns auf Social Media: ----

➜ Danke fürs Abo & fürs Zusehen!