CONCEPT Cited by 1 source
Tier topology as branch hierarchy¶
Definition¶
Tier topology as branch hierarchy is the architectural principle that deployment environments (production, staging, UAT, QA, etc.) should be modeled as long-running branches within a single database parent rather than independent database instances. The parent-of chain between branches defines the promotion path; feature branches are ephemeral descendants of a tier that get cleaned up after merge.
This reframes environment management from fleet operations (provision, patch, sync N instances) to branch policy (declare hierarchy, inherit governance, merge to promote). A six-environment instance world collapses to one parent with a branch hierarchy, eliminating drift, provisioning cost, and environment-specific configuration.
Key properties¶
- Tiers are long-living branches with declared parents
- Features are ephemeral branches descending from a tier
- The parent-of chain is the promotion hierarchy
- Schema diff between any two tiers is a computable operation (not a cross-instance comparison)
- Branch names are arbitrary; the parent-of conventions are what matters
Seen in¶
- systems/lakebase — environments as branches of a single Lakebase parent (Source: sources/2026-06-12-databricks-enabling-evolutionary-database-development-database-branchin-part3)