🏗️Structural Changes

NEW

Also known as: Schema Changes, Breaking Changes

Modifications to database or table structure, such as adding columns, changing data types, or altering constraints.

DESCRIPTION

Structural changes alter schemas and contracts between producers and consumers. Typical operations include adding or dropping columns, type changes, constraint updates, and index modifications. Safe evolution favors backward-compatible changes and clear deprecation paths. Migration tooling orchestrates DDL with rollbacks across environments. Data formats and registries enforce compatibility rules for streaming and batch pipelines. Testing and lineage help assess downstream impacts. Governance requires communication, approvals, and versioned documentation.

ALTERNATIVE DEFINITIONS

Apache Iceberg

Schema evolution is the ability of a table to handle changes to the schema over time.

Highlights evolving table schemas with a focus on long-term compatibility.

Source

Confluent

Schema evolution allows changes to a schema while maintaining compatibility between producers and consumers.

Emphasizes compatibility governance in event-driven systems.

Source

RELATED TERMS

Schema Evolution Model Data Migration DDL Liquibase Flyway Apache Iceberg Confluent Schema Registry Versioning

COMPETING TERMS

Row Level Changes

KNOWLEDGE AREAS

Data Architecture Data Modeling Data Engineering Data Storage & Operations Testing & Validation

TARGET AUDIENCE

Data Engineer Data Architect Data Modeler DevOps Engineer Analytics Engineer

EXTERNAL SOURCES

• Wikipedia - Database schema
• Liquibase - Database change management concepts
• Redgate - Database version control guidance
• Martin Fowler - Contracts to manage change impact

TOP QUESTIONS

What makes a Structural Change breaking?

Removing fields, changing types incompatibly, or altering semantics without migration breaks consumers.

Category: Risks

How to safely introduce Structural Changes?

Prefer additive changes, version contracts, run dual-write/read periods, and communicate deprecations.

Category: Requirements

Which tools manage Structural Changes?

Liquibase, Flyway, Schema Registry, and migration frameworks orchestrate and validate changes.

Category: Example

How does lineage help Structural Changes?

It reveals downstream dependencies, guiding impact analysis, testing scope, and communication plans.

Category: Example

What tests catch Structural Change issues?

Schema compatibility tests, contract tests, and migration dry runs prevent runtime failures.

Category: Testing

When to avoid Structural Changes?

If semantics are unclear or dependencies unknown, postpone until impact is understood and mitigations exist.

Category: Opinion

How to document Structural Changes?

Maintain versioned migration scripts, changelogs, and updated models in the catalog.

Category: Management

Do Structural Changes require approval?

Yes, changes to contracts typically undergo governance review and stakeholder sign-off.

Category: Requirements

How do streaming systems handle Structural Changes?

Schema registries enforce compatibility modes and coordinate producer–consumer upgrades.

Category: Example