Zero downtime Postgres migration, done right
engineering.theblueground.com
Zero downtime Postgres migration, done right
1–10 of 135 posts
Re: Zero downtime Postgres migration, done right
#2fyi the hyperlink "found here" to setup_new_database.template is broken.
Re: Zero downtime Postgres migration, done right
#3Re: Zero downtime Postgres migration, done right
#4Re: Zero downtime Postgres migration, done right
#5Looking for something similar for a mariadb setup. Anyone knows some resources?
Re: Zero downtime Postgres migration, done right
#6This app apparently had robust enough retry mechanisms that they were able just eat the errors and not have customer issues—Color me impressed! I'm not sure how many teams can make that claim; that's a hard thing to nail down.
Re: Zero downtime Postgres migration, done right
#7I looked at the company, and while they seem rather large, they're not Netflix or AWS.
I imagine they need to be up for people to be able to check in, etc. But they could just block out the planned maintenance as check in times far in advance. I'm sure there's a million other edge cases but those can be thought out and weighed against the engineering effort.
Don't get me wrong, this is very cool.
But I wonder what the engineering cost was. I'd think easily in the hundreds of thousands of dollars.
Re: Zero downtime Postgres migration, done right
#8Very interesting article. But I have to ask: would taking down the system for a couple of hours be that bad? I looked at the company, and while they seem rather large, they're not Netflix or AWS. I imagine they need to be up for people to be able to check in, etc. But they could just block out the planned maintenance as check in times far in advance. I'm sure there's a million other edge cases but those can be though…
Re: Zero downtime Postgres migration, done right
#9Re: Zero downtime Postgres migration, done right
#10Braintree (IIRC) had a really clever migration strategy, although I can't seem to find the blog post now. They paused all traffic at the load balancer, cut over to the new DB, and then resumed traffic. No requests failed, just a slight bump in latency while the LBs were paused. This app apparently had robust enough retry mechanisms that they were able just eat the errors and not have customer issues—Color me impresse…