Even though Kubernetes is the “next cool thing”, I still see many customers sticking with Broadcom/VMware as the underlying layer. Having been a vSpecialist for over 10 years, I can relate: It is an amazing piece of middleware. Don’t have a third DC, but still want to install Kubernetes across two? With VMware vSphere, you can!
Continuing the brief history of metro from part 2 of the series with some things that really help in building out a
In the previous “a brief history of metro” blog post (part 1) I discussed replication and metro and how they are “the
You may ask yourself: Why blog about a VMware environment? In parallel to “learn to crawl before you run” I feel that a lot of people working with kubernetes have a requirement (or at least THINK they have a requirement) for active/active metro storage solutions under their kubernetes setup. Building out a metro environment seems really easy, but as I run through this series you’ll discover that metro is anything-but-simple; there are many things to consider… Things that VMware figured out in their stretched cluster setup where kubernetes will struggle. I hope that people will start to see what metro is all about when I revisit the world of Virtual Machines.
In order to fully understand metro configurations, let’s first look at the history of things. The earliest ways of recovering from datacenter
There are many ways to obtain resiliency in the world of cloud-native applications. Some prefer to handle everything in the app-layer (this