Moving from Heroku to Google Kubernetes Engine

Re:Moving from Heroku to Google Kubernetes Engine by pm90 on Thursday April 04, 2019 @11:12PM (#19579342)

They mentioned that there will be some interesting updates next week for Google Next; do you think your feelings might change if they announced support for newer versions and point-in-time recovery?

On a related note, if you have tried it, what do you think of their Cloud SQL MySQL offering?

[ Parent | on HN ]

Re:Moving from Heroku to Google Kubernetes Engine by Spartan-S63 on Friday April 05, 2019 @12:10AM (#19579624)

Not the original commenter, but my team uses CloudSQL MySQL. It's not too bad. It's pretty performant, but we've run into some weird issues surrounding replicas.

As far as I know, MySQL 5.7 is as far as they go and like PostgreSQL, they don't support point-in-time recovery. Also, perplexingly (at least as of a year ago?), deleting the instance deletes all backups associated with it, so there's an opportunity to accidentally blow away all your data. I'm sure Google can recover it, but you'll have to submit a support ticket for that.

[ Parent | on HN ]

Re:Moving from Heroku to Google Kubernetes Engine by takeda on Friday April 05, 2019 @12:49AM (#19579792)

Yes, when deleting an instance you can't reuse the same name for a week, so I'm quite sure it is there for at least that amount of time.

[ Parent | on HN ]

Re:Moving from Heroku to Google Kubernetes Engine by wrs on Friday April 05, 2019 @11:53AM (#19583745)

At this point I’m reluctant to commit to it without evidence that they’ll keep it up to date. They can upgrade to v11, but how do I know it won’t still be at v11 in 2021?

We don’t use MySQL.

[ Parent | on HN ]