Tobi Knaup and Gou Rao on stateful containers

Why stateful services are an important part of the future of containers and microservices in the enterprise.

By Jeff Bleiel
March 8, 2018
Shadow boxes Shadow boxes (source:

In this episode of the O’Reilly Podcast, I talk about issues surrounding stateful containers and services with Tobi Knaup, CTO and co-founder of Mesosphere, whose DC/OS is a platform for deploying stateful and stateless applications on any combination of infrastructure, and Gou Rao, CTO of Portworx, a provider of persistent storage for containers.

Learn faster. Dig deeper. See farther.

Join the O'Reilly online learning platform. Get a free trial today and find answers on the fly, or master something new and useful.

Learn more

Discussion points:

  • The differences between stateful and stateless containers, and the reasons why “you need both stateless applications and stateful data services to build a modern, data-driven application,” according to Knaup.
  • Why increased agility—the ability to build applications that are more resilient and scalable—is the primary business case for running stateful services on container platforms.
  • Knaup and Rao offer their advice on how organizations should start if they’re interested in incorporating containerized stateful services into their architectures. Knaup says, “Decouple what you’re running from why you’re running it, and pick a platform that allows choice of different data services, and run it on whatever infrastructure you need. Rao says, “Choose a product that has metrics in place, that understands how to do things cloud-natively, at container granularity.”

This post is a collaboration between Mesosphere and O’Reilly. See our statement of editorial independence.

Post topics: Software Architecture