#238: You might just now be reaching the point of containerizing your workloads and running them in Kubernetes. However, how do you go about accessing those workloads? You might have started with an ingress, because other options seemed like they were too complex.
However, you’ve now crossed the point where you need that complexity. That’s where service mesh can help you out.
On this episode, we speak with Marino Wijay, Principal Developer Advocate at solo.io, about how service mesh has evolved over time, the challenges of adopting certain models, and the advantages of open-source solutions. We also talk about the differences between sidecar and sidecar-less models, and the circumstances in which either might be appropriate.
Marino Wijay is a Canadian, Traveller, International Speaker, Open Source Advocate for Service Mesh, Kubernetes, and Networking. He is an Ambassador @ EddieHub, and Lead Organizer for KubeHuddle Toronto. He is passionate about technology and modern distributed systems. He will always fall back to the patterns of Networking and the ways of the OSI. Community building is his driving force; A modern Jedi Academy.
Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.
His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).
He often speaks at community gatherings and conferences (latest can be found here).
His random thoughts and tutorials can be found in his blog TechnologyConversations.com.
If you like our podcast, please consider rating and reviewing our show! Click here, scroll to the bottom, tap to rate with five stars, and select “Write a Review.” Then be sure to let us know what you liked most about the episode!
Also, if you haven’t done so already, subscribe to the podcast. We're adding a bunch of bonus episodes to the feed and, if you’re not subscribed, there’s a good chance you’ll miss out. Subscribe now!