Delivering Database Changes

BackerLeader 15 110 214
calendar_todayschedule1 min read

Tony Kelly hosts our latest episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton.

While application code deployments have become highly automated and disciplined, database changes often remain manual, "folksy," and prone to causing messy environment drift. Find out why databases require a uniquely cautious approach due to the severe risks of data loss and the impossibility of simple rollbacks, emphasizing the need to treat database deployments with the same rigor as application code.

Listen to find out more about:

  • Why databases are fundamentally different
  • Crucial first steps for modernization
  • State-based versus Migration-based approaches
  • Tooling and Automation
  • Test Data Management
  • Database Refactoring Patterns
  • Real-world disaster stories
Part 7 of 10 in CD Office Hours
🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

Am I Deployable?

Steve Fentonverified - Jul 1

Pocket DB - Single-file, NoSQL database.

Fabien B. - Aug 10

The Hidden Program Behind Every SQL Statement

lovestaco - Apr 11

Prioritizing Continuous Delivery

Steve Fentonverified - Jun 24

EKS Auto Mode: What It Actually Changes (and What It Doesn’t)

Alexandre Vazquez - Jul 27
chevron_left
14.3k Points339 Badges
95Posts
148Comments
67Connections
Steve Fenton is an Octonaut at Octopus Deploy. He’s a Software Punk, author, programming-architect, ... Show more

Related Jobs

View all jobs →

Commenters (This Week)

1 comment
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!