Skip to content

Liquibase Strategy

Purpose

Liquibase is the preferred future database migration tool for Algosure PostgreSQL schema changes.

Position

Topic Standard
Migration tool Liquibase.
Ownership ChangeSets are owned by the module that owns the affected data.
Review ChangeSets require database, architecture, and security review where risk warrants.
Traceability ChangeSets reference work item, module, and purpose.
Safety Destructive changes require explicit approval and verification plan.

Future Changelog Organization

Future implementation should organize Liquibase changelogs so ownership is visible by module. The final folder layout is not defined here.

flowchart TB
    Root[Master Changelog]
    Identity[identity changelog]
    Organization[organization changelog]
    Bid[bid changelog]
    Analytics[analytics changelog]

    Root --> Identity
    Root --> Organization
    Root --> Bid
    Root --> Analytics

ChangeSet Rules

  • One ChangeSet has one clear purpose.
  • ChangeSet IDs are stable.
  • ChangeSets must not be edited after release except under governed remediation.
  • Preconditions should protect risky assumptions where practical.
  • Rollback notes or recovery guidance are required for risky changes.
  • Data backfills must be tenant-aware where customer data is involved.

Non-Goals

This document does not create Liquibase files, naming conventions, contexts, labels, checksums policy, or CI integration.