Episode

Who needs a server?

Podcast
Adventures in DevOps
Published
May 1, 2026
Duration seconds
3318
Processing state
failed
Canonical source
https://adventuresindevops.com/episodes/271-serverless-who-needs-a-server-no-server-required
Audio
https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/71842506/download.mp3
JSON
/v1/public/podcasts/adventures-in-devops/episodes/who-needs-a-server
Markdown
/podcast/adventures-in-devops/who-needs-a-server.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/adventures-in-devops/episodes/who-needs-a-server/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/adventures-in-devops/who-needs-a-server.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Share Episode                     Founder of Bespinian and long-time cloud solutions architect, Lena Fuhrimann, sits down with us to clarify the widespread confusion around serverless architecture. We discuss how serverless is often incorrectly equated solely with Function as a Service (FaaS), when it actually represents a broader spectrum on the abstraction ladder—including managed AI inference, container platforms, and databases.           Lena shares her early career traps of building a fragmented landscape of sixty "nano-services" and explains why starting with a well-architected monolith and progressively breaking out microservices based on distinct resource or lifecycle requirements is a much saner approach. Then we shift to drivers behind cloud migrations, emphasizing that the primary financial benefit of serverless isn't necessarily shrinking the monthly cloud provider bill, but rather optimizing your most expensive resource: engineering time. By offloading mundane infrastructure patching to the cloud provider, teams can focus entirely on delivering tangible business value to customers. But cost is still there too.           We also explore the psychological challenges of adopting new paradigms, sharing a fascinating story of bridging the gap for a VM-loving engineer by introducing immutable infrastructure concepts through Packer and Ansible before fully transitioning them to containers. And of course we tackle the dreaded topic of "cold starts" and why complex workarounds—like building custom Lambda warmers to periodically call APIs—often defeat the core benefits of reduced total cos…