sonichigo

When we think about CI/CD, the database is often a blind spot. I wrote this post to explore why this is so risky and what makes database changes so different from application code. The article dives into the unique challenges, from black-box migrations to performance regressions—and how we can begin to address them by shifting observability left!

We're validating our approach for database GitOps and noticing that traditional branching-per-environment models often introduce significant friction:

1. Merge conflicts across dev, qa, prod branches 2. Inconsistent baselines and forgotten hotfixes 3. Broken audit trails and configuration drift

We shifted instead to a trunk-based approach with Liquibase contexts:

1. All changes stored in one main branch 2. Environment-specific behavior driven by context metadata 3. Promotions handled via pipelines, not merges 4. Full GitOps traceability and one-click rollback support

We’ve been reevaluating our Git strategy for database changes. Historically, our team maintained one branch per environment—dev, qa, and prod. While it gave us some flexibility, it created a lot of overhead: merge conflicts, forgotten hotfixes, and inconsistent deployment behavior.

Recently, we adopted a trunk-based model paired with Liquibase for change management. Instead of branching per env, we:

Keep all changelogs in a single main branch Use Liquibase contexts to control env targeting Promote via automated pipelines Apply GitOps principles for traceability and rollback

Curious—how are others approaching Git branching for DB changes? Is anyone still using GitFlow or feature/env branches? Anyone managing this at scale with other tools like Flyway or Atlas?

Would love to hear real-world stories.

Thanks for the feedback, I'll work on to fix this and update it

DeepCoder-14B is quietly outperforming some of the biggest coding LLMs out there—including o3-mini—and it’s open source from top to bottom.

Find out how a lean 14B model, trained on real-world problems and refined with smart RL techniques, is changing the game.