Interact: ServiceMesh and MultiCloud Demystified – Part 1

clipboard image 1756196587 - FULLSTACKS

Idea, Motivation, and Background

Everyone is talking about “Mutlicloud” and wants to operate “every workload at every location.” We don’t just talk about it – we do it too! In the last blog post on the Cloud Native App Journey “Interact,” we addressed this topic.

This blog post directly addresses the topic of “Interact” and its implementation via ServiceMesh, ServiceDiscovery, and “Multi Cloud|Platform” connectivity.

But first things first:

It certainly makes sense to place a workload where it is “best” suited. If we compare “the cloud” to a “hotel,” the current standard is often Kubernetes. Kubernetes is the operating system for applications in the cloud and enables state-of-the-art operation of applications and the mapping of their life cycle.

But not all applications are per-se containerized or even microservices. Furthermore, many fundamental questions arise. Because the central challenge is that all applications – especially the modern ones – must communicate with other applications – across various platforms.

What are the essential questions that arise:

  • How do you connect the individual platforms (clouds, data centers, VMs, containers, etc.) in reality?

  • What challenges exist with regard to the network?

  • How do you implement security with real zero-trust networking and encryption?

  • How do you automate networking and relieve Dev and Ops?

  • How do the applications or the individual components find each other when they are operated in a distributed manner (keyword: ServiceDiscovery)?

At this point, you end up with the topics: Service Mesh & Service Discovery

Global Galactic Challenge

Cloud. Container. Kubernetes. Microservices. Lift and shift. Re-factor, Re-architect. Cloud-native app journey. That’s all great, and they are technologies that can bring us a lot of value – if we use them correctly.

But it is complete nonsense if we tell people for every new technology that they have to rebuild their stuff – or even completely rebuild it. That destroys synergy. Everything must happen with sense, reason, and a corresponding portion of pragmatism.

And we say that as technologists.

Let’s start at the very beginning – what is today’s IT about?

Development from Monoliths to “Cloud Native Applications”

How Did it all Begin?

With individual, physical servers

- FULLSTACKS

 

This was followed by virtual machines (and then dynamic VMs – e.g., with OpenNebula, Terraform, AWS EC2, etc.)

- FULLSTACKS

 

And then the even smaller, short-lived containers

- FULLSTACKS

 

And that’s what the whole fleets of microservices are made of

fullstacks Wie hat alles angefangen 4 4 - FULLSTACKS

What Challenges Have Arisen?

  • How do you migrate from a monolith to microservices?

  • How do you secure the communication between the services?

  • How do you deal with stateful applications?

  • In addition, there are the organizational challenges such as Conway’s Law (https://de.wikipedia.org/wiki/Gesetz_von_Conway)

A slightly more technical representation using a simple example:

The (internal) function calls within a monolith now migrate as a Remote Procedure Call (RPC) over a network:

 

And networks are known to be super secure and stable – especially in the cloud and between data centers. NOT.

In addition, there are challenges such as “Multi Platform” – or “Multi Cloud”

The services of a Kubernetes cluster should be able to communicate with bare-metal servers, VMs, containers, or serverless functions / cloud services

How Do You Connect all these Different Platforms with each other?

  • Without vendor lock-in?

  • Without massive overhead and complexity in operation?

  • With Security / Zero-Trust?

The essential, technical challenges:

  • Service Discovery – how do the services find each other?
  • Security which service is allowed to speak to which (via secure mTLS)?
  • Routing – How is routing done to the individual services?

With that, we have roughly outlined the essential basics and features of a service mesh.

In detail, we will clarify these points and questions in the following blog posts.

More Blog Posts