Code Story episode
S7 E30: The Architecture of Infinite Scale: Harnessing Vitess and Database Sharding with Sam Lambert of PlanetScale
Apr 4, 2023 · Season 7 · Episode 30 · 22 min
The last database platform you will need
Sam Lambert is originally from the UK, and has lived quite a few places during his life. He went to school in India, but now resides in San Francisco. He finds software to be a creative, playful process, and sees people trying to build that away from the process. He feels very lucky to building something that provides fruit and solves problems. Outside of tech, he is married with a 4 year old, and is into cooking and art. I asked about NFT's, given his tech background, but he's not super into that form of art at this time.
Sam spent time working at Github as a VP of Engineering, specifically focusing on infrastructure. He and his team came across Vitess, the backend that ran YouTube, and he took this amazing framework into his current venture to remix their approach of design and scalability.
This is the creation story of PlanetScale.
Sponsors
AirbyteDopplerHost.ioIPInfomablSupportZebraLinks
Website: https://planetscale.com/LinkedIn: https://www.linkedin.com/in/isamlambert/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Startup engineering team structure that actually ships
How to structure a startup engineering team: the models that work at 5, 15 and 40 engineers, how to split teams, and the org mistakes that quietly slow delivery.
How to choose a tech stack for a startup
A decision framework for choosing a startup tech stack: what actually matters, which choices are reversible, and how to avoid the rewrite that eats your Series A.
Build vs buy: a decision framework for technical leaders
When to build software in-house and when to buy it: a build vs buy framework covering total cost of ownership, differentiation, switching costs and vendor risk.