A closer look at database branches: how they work and what to keep in mind when choosing a serverless database provider.
A more detailed look at database branching and provider offerings can be found in the report.
Branch Types
A database branch is like a Git branch, but it includes two distinct attributes: data and schema. Different providers offer different types when creating branches.
| Provider | Data + Schema | Schema Only |
|---|---|---|
| Neon | ||
| Supabase | ||
| PlanetScale |
Branching Workflows
A database branch can be linked with a codebase branch so database and application changes are synced. This can be helpful in one-to-one relationships, but can be unhelpful in one-to-many.
| Provider | Linked with Codebase branch |
|---|---|
| Neon | |
| Supabase | |
| PlanetScale |
Branch Creation Speed
Creating a codebase branch is usually instant but, creating a database branch, of any type, can take longer than expected, which could impact developer productivity.
Branch Branching
On occasion you won't want to branch directly from the main branch, but instead, you may want to branch from an existing branch. Creating a branch for development, testing or staging for instance.
| Provider | Branch from branch |
|---|---|
| Neon | |
| Supabase | |
| PlanetScale |
Resource Isolation
Sharing CPU/RAM between branches can lead to noisy neighbor problems. A more performant approach is for each branch to have its own dedicated resource.
| Provider | Isolated Resource |
|---|---|
| Neon | |
| Supabase | |
| PlanetScale |
Branching Costs
A branch uses the same resources as a new database, sometimes making it subject to billing. Some providers restrict branching to paid plans often with unpredictable pricing.
| Provider | Available to free tier | predictable pricing |
|---|---|---|
| Neon | ||
| Supabase | ||
| PlanetScale |