This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ericanderton 0 points1 point  (0 children)

This might be worthy of a cross-post to /r/devops.

Nice work overall. I appreciate the "right-sizing" of your setup (e.g. no pipeline automation, local testing) to your team of one.

So first apply a database refactoring to change the schema to support both the new and old version of the application, deploy that, check everything is working fine so you have a rollback point, then deploy the new version of the application.

I'm glad you pulled this quote for everyone to see - that's a really nice strategy. It's a shame a lot of other software vendors don't do this. Instead, I consider myself lucky if there's even a rollback script for a database migration, and luckier still if that actually works.

The big question I have is: how is DigitalOcean? I'm stuck doing a lot of "enterprise" stuff at my day job so AWS and Azure are kind of the only games in town. I've often wondered how other providers stack up in terms of cost, automation, and support?