Summary
Application architectures have been in a constant state of evolution as new infrastructure capabilities are introduced. Virtualization, cloud, containers, mobile, and now web assembly have each introduced new options for how to build and deploy software. Recognizing the transformative potential of web assembly, Matt Butcher and his team at Fermyon are investing in tooling and services to improve the developer experience. In this episode he explains the opportunity that web assembly offers to all language communities, what they are building to power lightweight server-side microservices, and how Python developers can get started building and contributing to this nascent ecosystem.
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 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. And now you can launch a managed MySQL, Postgres, or Mongo database cluster in minutes to keep your critical data safe with automated backups and failover. 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!
- Need to automate your Python code in the cloud? Want to avoid the hassle of setting up and maintaining infrastructure? Shipyard is the premier orchestration platform built to help you quickly launch, monitor, and share python workflows in a matter of minutes with 0 changes to your code. Shipyard provides powerful features like webhooks, error-handling, monitoring, automatic containerization, syncing with Github, and more. Plus, it comes with over 70 open-source, low-code templates to help you quickly build solutions with the tools you already use. Go to dataengineeringpodcast.com/shipyard to get started automating with a free developer plan today!
- Your host as usual is Tobias Macey and today I’m interviewing Matt Butcher about Fermyon and the impact of WebAssembly on software architecture and deployment across language boundaries
Interview
- Introductions
- How did you get introduced to Python?
- For anyone who isn’t familiar with WebAssembly can you give your elevator pitch for why it matters?
- What is the current state of language support for Python in the WASM ecosystem?
- Can you describe what Fermyon is and the story behind it?
- What are your goals with Fermyon and what are the products that you are building to support those goals?
- There has been a steady progression of technologies aimed at better ways to build, deploy, and manage software (e.g. virtualization, cloud, containers, etc.). What are the problems with the previous options and how does WASM address them?
- What are some examples of the types of applications/services that work well in a WASM environment?
- Can you describe how you have architected the Fermyon platform?
- How did you approach the design of the interfaces and tooling to support developer ergonomics?
- How have the design and goals of the platform changed or evolved since you started working on it?
- Can you describe what a typical workflow is for an application team that is using Spin/Fermyon to build and deploy a service?
- What are some of the architectural patterns that WASM/Fermyon encourage?
- What are some of the limitations that WASM imposes on services using it as a runtime? (e.g. system access, threading/multiprocessing, library support, C extensions, etc.)
- What are the new and emerging topics and capabilities in the WASM ecosystem that you are keeping track of?
- With Spin as the core building block of your platform, how are you approaching governance and sustainability of the open source project?
- What are your guiding principles for when a capability belongs in the OSS vs. commercial offerings?
- What are the most interesting, innovative, or unexpected ways that you have seen Fermyon used?
- What are the most interesting, unexpected, or challenging lessons that you have learned while working on Fermyon?
- When is Fermyon the wrong choice?
