TechPrufer
Get started
PlanetScale
PlanetScale logoPlanetScale · Feature trail

Relational Database Schema Design

2 posts · Jul 2021 – Mar 2022

What this trail covers

PlanetScale offers a Git-like workflow for database schema changes, enabling safe, non-blocking, and rolling upgrades. This approach aims to reduce the operational friction associated with traditional RDBMS schema management, giving developers ownership and velocity. The system provides mechanisms for managing metadata changes, handling potential production risks, and facilitating developer-friendly schema evolution.

All PlanetScale trails
  1. Database schema design 101 for relational databasesThis post provides a foundational guide to relational database schema design. It breaks down the process into four key steps: understanding business needs, identifying entities (tables), defining properties (fields and primary keys), and establishing relationships (foreign keys). It uses a retailer example to illustrate these concepts and introduces ERDs as a design tool. The post concludes by linking schema design safety to PlanetScale's branching feature.
  2. The promises and realities of the relational database modelThis post elaborates on the challenges of traditional relational database schema management, particularly the operational overhead and developer friction. It contrasts historical DBA-centric approaches with modern CI/CD demands, highlighting issues like metadata locking, manual tooling, coordination needs, and the lack of undo capabilities. The post positions PlanetScale's approach as a solution to these problems, emphasizing developer ownership and a more integrated schema change workflow.