Summary

Communication is a fundamental requirement for any program or application. As the friction involved in deploying code has gone down, the motivation for architecting your system as microservices goes up. This shifts the communication patterns in your software from function calls to network calls. In this episode Idit Levine explains how the Gloo platform that she and her team at Solo have created makes it easier for you to configure and monitor the network topologies for your microservice environments. She also discusses what developers need to know about networking in cloud native environments and how a combination of API gateways and service mesh technologies allow you to more rapidly iterate on your systems.

Announcements

• Hello and welcome to Podcast.init, the podcast about Python’s role in data and science.

• When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With the launch of their managed Kubernetes platform it’s easy to get started with the next generation of deployment and scaling, powered by the battle tested Linode platform, including simple pricing, node balancers, 40Gbit networking, dedicated CPU and GPU instances, and worldwide data centers. Go to pythonpodcast.com/linode) and get a $100 credit to try out a Kubernetes cluster of your own. And don’t forget to thank them for their continued support of this show!

• Your host as usual is Tobias Macey and today I’m interviewing Idit Levine about what developers need to know about service-oriented networking and her work at Solo on the Gloo project

Interview

• Introductions

• How did you get introduced to Python?

• Can you describe what Solo is and the story behind it?

• How much should developers need to know about the ways that their applications and services are communicating?

• What is the current state of networking for applications across physical, cloud, and containerized environments?

• How do service mesh features influence the architectural decisions that software teams make while building their applications?

• What operational capabilities do they unlock?

• What are the aspects of application networking that are simplified or enhanced by service mesh platforms?

• In what ways has service mesh introduced new complexity to operating software systems?

• How can developers mirror the network topologies for production environments while working on new features?

• What are the most interesting, innovative, or unexpected ways that you have seen Gloo used?

• What are the most interesting, unexpected, or challenging lessons that you have learned while working on Gloo?

• When is Gloo the wrong choice?

• What do you have planned for the future of Gloo?

Keep In Touch

• LinkedIn)

• @Idit_Levine) on Twitter

Picks

• Tobias

• Shadow and Bone) on Netflix

• Idit

• Elizabeth Holmes HBO Documentary)

Closing Announcements

• Thank you for listening! Don’t forget to check out our other show, the Data Engineering Podcast) for the latest on modern data management.

• Visit the site) to subscribe to the show, sign up for the mailing list, and read the show notes.

• If you’ve learned something or tried out a project from the show then tell us about it! Email [email protected])) with your story.

• To help other people find the show please leave a review on iTunes) and tell your friends and co-workers

Links

• Solo)

• Computational Biology)

• Microservices)

• Kubernetes)

• Service Mesh)

• Istio)

• LinkerD)

• Envoy Proxy)

• API Gateway)

• CRD == Custom Resource Definition)

• Gloo Edge)

• Bazel Build System)

• GraphQL)

• mTLS)

• GitOps)

• Dagger)

• WASM == Web Assembly)

• Kubernetes Gateway API)

• Consul Connect)

• eBPF)

The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra) / CC BY-SA)