Post

Why would I talk you out of a good idea?

One problem is that you are going to have your app and database in different data centers (or maybe regions) and that means you will add latency. Are you dure you want to di that? Better migrate off Heroku then

I think they both use the same AWS region. Right @benediktdeicke.com ??

I did this last year. Just make sure they are in the same region and you should be fine.

How long was your downtime? And how many GB was your database?

We were less than 10gb. And I was able to do a full backup after hours and just a switch over the url.

It was a nice concierge migration for my big database and easy SEO migration for my staging.

Doh, *self migration for staging.

Why?

That is a good question! A couple of reasons. I can create multiple databases so I can migrate to solid queue easier (Redis is overkill for my low scale app). Several people told me already that CD is way faster. The biggest reason, I'm starting to trust Heroku a bit less these days.

How can't you create another postgres add-on on heroku for solid queue?

And I only hear good stories about CD. The biggest one is that you actually get customer service if you need it. If Heroku stops working, I can migrate relatively easy to something else. (if DB is not at Heroku)

I don't really know CD to be honest, so I'm more just curious, but wouldn't it mean you'd have to host their DB on one of the big clouds as opposed to Heroku? That might introduce some latency, no? Not that that's necessarily a dealbreaker 😅

We love Crunchy at Honeybadger. Do it! :)