Feature Request: Native Database Branching (Git-like, Copy-on-Write Snapshots)

[hkemon]

Description:
I would like to request the implementation of a native database branching feature in CockroachDB, similar to Neon’s branching model (Neon Branching Docs). The feature would allow users to:

• Create lightweight branches (snapshots) of a database at a given point in time.
• Work on these branches independently without affecting the main database.
• Merge changes back into the main database or other branches.

Motivation:
This feature would greatly enhance development workflows, enabling:

• Safe experimentation on production-like data.
• Git-like workflows for databases, useful for testing, staging, and feature development.
• Easier collaboration between developers with isolated database states.

Currently, while CockroachDB provides MVCC and AS OF SYSTEM TIME, these mechanisms allow only historical access and require manual backup/restore workflows to simulate branching. A native implementation would simplify these workflows and bring CockroachDB closer to modern developer expectations for branching/versioning in databases.

Suggested Features / Requirements:

1. Lightweight, copy-on-write branches that do not duplicate the entire database unnecessarily.
2. Ability to merge branches with conflict resolution support.
3. Optionally, integration with AS OF SYSTEM TIME to reference historical states when creating branches.
4. Support for branch lifecycle management (create, delete, list, merge).

Use Cases:

• Development and testing of features on real production data without risking the main database.
• Creating staging environments quickly for QA or performance testing.
• Versioned experimentation, rollback, and collaborative workflows.

References:

• Neon Database Branching: https://neon.com/docs/introduction/branching

I believe this feature would be a valuable addition to CockroachDB and greatly improve developer productivity and operational flexibility.

Jira issue: CRDB-55387

[blathers-crl]

Hello, I am Blathers. I am here to help you get the issue triaged.

It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.

I have CC'd a few people who may be able to assist you:

• @cockroachdb/disaster-recovery (found keywords: backup,restore)
• @cockroachdb/kv (found keywords: MVCC)

If we have not gotten back to your issue within a few business days, you can try the following:

• Join our community slack channel and ask on #cockroachdb.
• Try find someone from here if you know they worked closely on the area and CC them.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[blathers-crl]

cc @cockroachdb/disaster-recovery

[hkemon]

Is it possible to implement this feature in CockroachDB, and if so, do you have a plan for its implementation? @msbutler

[gtracer]

Also very interested in having data branching in Cockroach