This is a parody of all things Silicon Valley: an epic tale about Theo, a real (fictional) hipster, and the twists and turns of his “disruptive” startup. As it turns out, making the world a better place by becoming seemingly rich is more difficult than it seems.
Gender diversity in the open source software community was a topic of discussion at this week’s KubeCon, where panelists explored the problem and pointed to corporations as safe havens against bad behavior.
It wouldn’t be a stretch to say that Istio popularized the concept of a “service mesh”. Before we get into the details on Istio, let’s briefly dive into what a service mesh is and why it’s relevant. We all know the inherent challenges associated with monolithic applications, and the obvious solution is to decompose them into microservices. While this simplifies individual services, connecting, monitoring and securing hundreds or even thousands of microservices is not simple. Until recently, the solution was to string them together using custom scripts, libraries and dedicated engineers tasked with managing these distributed systems. This reduces velocity on many fronts and increases maintenance costs. This is where a service mesh comes in.