Loading content
Liquibase is an open-source database schema change management tool that tracks, versions, and applies migrations across environments. It represents changes via changelogs in XML, YAML, JSON or SQL and integrates with CI/CD pipelines to automate deployments. It enables repeatable, auditable and reversible schema updates for teams.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Liquibase is a database migration tool that versions, validates, and deploys schema changes across different database systems.
Liquibase grew from the problem of managing database changes in deployed applications consistently and traceably. Its development progressed from declarative changeSets to rollbacks, validation, pipeline integration, and support for many databases.
Treat the schema like source code: a changeSet describes a small change with an author and identifier, Liquibase records applied changes in a history, and applies only new steps. A changelog orders those steps; rollback and validation rules reduce deployment risk.
It describes one uniquely versioned database change.
It orders changeSets into a deployable history.
It defines how to reverse a change in a controlled way.
Liquibase helps teams move schema changes with application code through development, test, and production environments. Backward compatibility, large tables, locks, and data migrations require planning before risky releases.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.