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!
Readit Newssonichigo commented on Observability for Databases in CI/CD blog.sonichigo.com/observ... · Posted by u/sonichigo
sonichigo commented on How are you handling Git branching for database migrations? harness.io/blog/how-git-s... · Posted by u/sonichigo
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
sonichigo commented on · Posted by u/sonichigo
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.
sonichigo commented on · Posted by u/sonichigo
Like many teams, we treated application CI/CD as a first-class citizen but left PostgreSQL schema changes as a manual afterthought. That led to broken deployments, inconsistent environments, and rollback nightmares.
This article shares our transition to a fully automated, GitOps-style workflow using Harness Database DevOps and Liquibase. It dives into technical challenges, architecture changes, and lessons learned while scaling PostgreSQL migrations across multiple environments.
Read the full blog post - https://dub.sh/JMUgbep
Would love to hear how others have tackled this problem at scale.
sonichigo commented on Running WebAssembly with containerd, crun, and WasmEdge on Kubernetes · Posted by u/sonichigo