cross-service-migration-coordination

What problem does it solve?

In the schema-per-tenant model, all services migrate against the same tenant database. This creates collision risks that must be managed.

Core Features & Use Cases

• Per-service migration tracking tables to avoid cross-service conflicts.
• Table prefixing strategy to prevent generic table name collisions across services (e.g., identity_, access_ctrl_).
• Migration execution order guidance and runner pattern to preserve dependencies across services.
• Use Case: When coordinating deployments across multiple services, use dedicated tracking tables and table prefixes to maintain isolation and reliability.

Quick Start

Configure and run per-service migrations in dependency order using isolated schema_migrations tables and prefixed domain tables.