Abstract
It is en vogue to divide applications into compartmentalized microservices and operate them in Kubernetes clusters. Strictly speaking, a Kubernetes cluster is a monolithic system consisting of inseparable services. This means that the individual services cannot be operated or switched off independently of each other. This concept is very reminiscent of the 90s with the concept of large application servers. It would be logical to adapt the operating concept to the software architecture: Offer independently operable infrastructure services. Such as service registry, deployment distribution, load balancing…
In this presentation, we would like to show how the microservice concept - small, self-contained, specialized building blocks - can also be implemented in infrastructure services and show and discuss alternatives to Kubernetes. We want to present use-case-oriented solution sketches.
Alternatives to Kubernetes by @SandraParsick and @sanddorn at #xpdays19 pic.twitter.com/MYEo7EvIwQ
— Thorsten Brunzendorf (@thbrunzendorf) November 7, 2019
#xdde19 .@SandraParsick and her colleague on why you don't need k8s everytime 😁 "just use the building Blocks you really need". Happy to have her a @softwerkskammer Nuremberg tonight. #swknbg pic.twitter.com/YVHrqio2vz
— Marco Emrich (@marcoemrich) November 7, 2019
