Thoughts on Google Cloud MySQL?

[csdude55]

I didn't know that this was a thing until about 30 minutes ago :-O

[cloud.google.com...]

It would be $42 /month for me.

The biggest advantages I can see, IF IT WORKS AS ADVERTISED!, is that it eliminates local problems that I have to fix, and faster processing time. And it frees up server space and resources, which (in theory) would make everything else run faster, too.

What do you all think?

[tangor]

If you don't mind g having all your content in hand (and get paid for it, too!) it's not a bad deal. Though $42/month is $504 (and probably add on junk fees as well) per year.

"faster" is found in the connection between user and site. Backend processing does not really impact that aspect.

[csdude55]

If you don't mind g having all your content in hand...

At this point, the Gods of Google have me wrapped around their finger, anyway. After COVID, my direct sales simply have not come back at all (seriously, I've gone from over 300 to 4, and most of my long time advertisers either went out of business or died). And even with my Google revenue being 1/5th of what it used to be, it's better than nothing.

I can justify $42 /month if it improves my page load time, eliminates down time from database crashes, or magically "improves" query time on some of my slower queries. If it's a lateral move, though, where all I'm doing is maintaining the data on a different URL, then it's harder to justify.

[tangor]

Should you opt to go that way please keep us informed of any value/increase in making that move.

Wishing the best!

[csdude55]

There's a webinar next Wednesday, I'll keep you posted.

[csdude55]

Minor update: the webinar wasn't a webinar at all! It was a pre-recorded video with very basic info, with a section to ask questions. There were a total of 4 questions asked (I was two of them), but no one replied.

It's been over 24 hours now, and I thought maybe someone would email with replies? But so far, no.

The only advantage seems to be auto-redundancy to guarantee no down time. But there was no explanation of how that would work (meaning, if server A is unresponsive and it bounces over to server B, and my users post something that is saved to server B, when server A comes back is it going to copy server B over before going live?), and no answer to whether that redundancy came with an extra cost.