Skip to main content
While migration-based workflow is powerful and flexible, be aware of these considerations:

Version Conflicts

Issue: Multiple developers creating migrations with the same version number. Solution: Use timestamp-based versioning (YYYYMMDDHHmmss) to avoid conflicts.

Migration Order Dependencies

Issue: Complex dependencies between migrations can be hard to manage. Solution:
  • Keep migrations small and focused
  • Use descriptive names
  • Document dependencies in comments
  • Consider state-based workflow for pure schema changes

Rollback Complexity

Issue: Reverting migrations requires writing reverse scripts. Solution:
  • Plan rollback strategy before deploying
  • Test rollback scripts in staging
  • Consider using Bytebase’s data rollback feature for DML changes

Data Rollback

Automatic rollback for INSERT/UPDATE/DELETE operations

Schema Drift Detection

Issue: Manual changes bypass GitOps and cause drift. Solution:
  • Restrict direct database access
  • Enable drift detection
  • Enforce all changes through GitOps

Drift Detection

Detect and manage schema drift

Large-Scale Deployments

Issue: Deploying to hundreds or thousands of databases takes time. Solution:
  • Use database groups for fleet management
  • Configure parallel execution limits
  • Enable sampling for validation (check N random databases)

Best Practices

Production-ready workflow patterns and optimizations

Next Steps