PlanetScale Postgres with CEO Sam Lambert

Key takeaways

PlanetScale has transitioned from being a MySQL-only company to offering Postgres due to customer demand and market needs.
The architecture of PlanetScale, supported by Vitess, allows for high scalability and reliability in database operations.
The company is adapting its technology stack and operational strategies to effectively support Postgres while maintaining a focus on performance.
Engagement with the Postgres community is vital for PlanetScale to enhance its offerings and address user feedback.
PlanetScale remains committed to its identity as a database provider, balancing innovation with reliability and performance.

Summary

Transition from MySQL to Postgres at PlanetScale

In this episode, Sam Lambert, CEO of PlanetScale, discusses the company's transition from being known primarily as a MySQL company to also offering Postgres. He explains the motivations behind this decision, driven by market demand and the need to accommodate new developer preferences, particularly among startups. The shift reflects broader trends in the industry and signifies PlanetScale's commitment to evolving its offerings to meet user needs.

Architectural Insights into PlanetScale

Sam explains the underlying architecture of PlanetScale, including the roles of Vitess and the different layers that make up the platform. He delves into technical intricacies such as sharding, node lifecycles, and the importance of maintaining operational discipline to ensure reliability and scalability. The conversation highlights the complexity of running distributed systems and the measures taken to prevent downtime.

Adapting the Platform for Postgres

The discussion moves to how the PlanetScale team has adapted its operational principles and technology stack to support Postgres. Sam describes the learnings from MySQL and how they are being applied to Postgres, emphasizing the need for reliability and performance. He outlines specific challenges like permissions management and the development of extensions to cater to the Postgres ecosystem.

Community Engagement and Insights

Sam expresses his excitement about entering the Postgres community and the warm reception PlanetScale has received. He talks about the importance of involving the community in product development and how user feedback is shaping future improvements. The company is focused on creating a reliable and performant Postgres offering tailored to the needs of its users.

The Future of PlanetScale and Strategic Focus

Towards the end of the episode, Sam discusses the strategic direction of PlanetScale, emphasizing the importance of staying focused on its core mission as a database provider while exploring opportunities in the Postgres landscape. He reflects on the competitive environment and the necessity for the company to remain humble and responsive to customer demands.

Show notes

Sam Lambert, my former boss at PlanetScale, talks to me about PlanetScale moving from a MySQL company to now also having a Postgres offering. Sam shares why PlanetScale decided to move to Postgres, how MySQL and Postgres are different at a technical level, and how the change has impacted the company culture. Stay to the end for a special surprise!

PlanetScale Metal Episode: https://youtu.be/3r9PsVwGkg4
Join the waitlist to be notified of the MySQL for Developers release on Database School:
https://databaseschool.com/mysql

Follow Sam:
PlanetScale: https://planetscale.com
Twitter: https://twitter.com/isamlambert

Follow Aaron:
Twitter: https://twitter.com/aarondfrancis
LinkedIn: https://www.linkedin.com/in/aarondfrancis
Website: https://aaronfrancis.com - find articles, podcasts, courses, and more.
Database School: https://databaseschool.com
Database School YouTube Channel: https://www.youtube.com/@UCT3XN4RtcFhmrWl8tf_o49g (Subscribe today)

Chapters:
00:00 - Inaugural episode on this channel
01:46 - Introducing Sam Lambert and his background
03:04 - How PlanetScale built on MySQL and Vitess
06:10 - Explaining the layers of PlanetScale’s architecture
09:57 - Node lifecycles, failover, and operational discipline
12:02 - How Vitess makes sharding work
14:21 - PlanetScale’s edge network and resharding
19:02 - Why downtime is unacceptable at scale
20:04 - From Metal to Postgres: the decision process
23:06 - Why Postgres vibes matter for startups
27:04 - How PlanetScale adapted its stack for Postgres
34:38 - Entering the Postgres ecosystem and extensions
41:02 - Permissions, security, and reliability trade-offs
45:04 - Building Ni: a Vitess-style system for Postgres
53:33 - Why PlanetScale insists on control for reliability
1:02:05 - Competing in the broader Postgres landscape
1:08:33 - Why PlanetScale stays “just a database”
1:12:33 - What GA means for Postgres at PlanetScale
1:17:43 - Call to action for new Postgres users
1:18:49 - Surprise!
1:22:21 - Wrap-up and where to find Sam