Branch your database like your code: How schema changes and pull requests go hand in hand
What if you could branch, test, and merge database schema changes directly within a pull request? Now you can.
#1about 2 minutes
Why database schema changes are harder than code changes
Traditional database schema migrations are imperative and stateful, making them fundamentally different and more complex than stateless code deployments.
#2about 7 minutes
How YouTube's scaling challenges led to the creation of Vitess
Vitess was created at YouTube to solve massive scaling problems by enabling horizontal sharding for MySQL and running it on Borg, the predecessor to Kubernetes.
#3about 8 minutes
The pain of merging database changes compared to Git
Unlike modern Git workflows, database schema changes often require manual review processes and can cause production downtime due to table locking and data dependencies.
#4about 2 minutes
Achieving non-blocking schema changes with shadow tables
Tools like GH-OST use shadow tables to apply schema changes to a copy of the table, sync ongoing writes, and perform an atomic cutover without locking production.
#5about 4 minutes
Applying a Git-like workflow to database schema changes
PlanetScale introduces database branches for isolated development and deploy requests, which function like pull requests for reviewing and merging schema changes safely.
#6about 5 minutes
Setting up a PlanetScale database with GitHub Actions
A live demonstration shows how to create a new repository from a template and use a GitHub Action to automatically provision a new PlanetScale database.
#7about 7 minutes
Creating a database branch from a GitHub pull request
This demo illustrates creating a pull request for a code change and then using a chat command to automatically create a corresponding database feature branch with a new schema.
#8about 5 minutes
Approving and merging schema changes via pull request comments
The demo concludes by showing how to review, approve, and merge a database deploy request directly from GitHub comments, triggering a non-blocking migration.
#9about 10 minutes
Exploring advanced Vitess features and answering questions
A summary of additional Vitess capabilities is followed by a Q&A session covering data residency, subquery performance, and deployment synchronization.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
01:55 MIN
Merging data engineering and DevOps for scalability
Software Engineering Social Connection: Yubo’s lean approach to scaling an 80M-user infrastructure
13:52 MIN
Q&A on GraphQL, team structure, and vendor software
Building high performance and scalable architectures for enterprises
26:30 MIN
Q&A: Key skills, complex projects, and the future of tech
Retooling and refactoring - an investment in people.
03:47 MIN
Applying software engineering practices to data pipelines
Enjoying SQL data pipelines with dbt
04:41 MIN
Boosting developer happiness and the future of self-service
Improving Developer Happiness with GitOps
03:33 MIN
Introduction to GitOps and the talk agenda
Get ready for operations by pull requests
04:29 MIN
Applying GitOps principles to network automation
How Cisco embraced a DevOps culture within its network engineering team
02:58 MIN
Analyzing Devin's automated pull request for the migration
WeAreDevelopers LIVE days are changing - get ready to take partStarting with this week's Web Dev Day edition of WeAreDevelopers LIVE Days, we changed the the way we run these online conferences. The main differences are:Shorter talks (half an hour tops)More interaction in Q&AA tips and tricks "Did you know" sect...
Dev Digest 134 - Where pixels sing?News and ArticlesWeAreDevelopers LIVE Data and Security Day is on Wednesday, 25/09/2024. Learn about OPC UA Updates, Best Practices for Using GitHub Secrets, Passwordless Web 1.5, Emerging AI Security Risks, Data Privacy in LLMs and get a chance to t...
Daniel Cranney
How Microsoft worked around a Git limitation to shrink a repository by 94%Imagine that you are responsible for a Git repository with 1000 users, and 20 million lines of code. You struggle to keep up with constant pull requests but the biggest problem is that the Git file size of the repository is mushrooming to over 170GB ...
From learning to earning
Jobs that call for the skills explored in this talk.