4 ms·

Can’t blame you for missing it given the length of the article, but there’s this paragraph towards the end: > I know I haven’t gone into a lot of specific deta

Can’t blame you for missing it given the length of the article, but there’s this paragraph towards the end: > I know I haven’t gone into a lot of specific details about GCP’s deprecations. I can tell you that virtually everything I’ve used, from networking (legacy to VPC) to storage (Cloud SQL v1 to v2) to Firebase (now Firestore with a totally different API) to App Engine (don’t even get me started) to Cloud Endpoints to… I dunno, everything, has forced me to rewrite it all after at most 2–3 years, and they never automate it for you, and often there is no documented migration path at all. It’s just crickets.

gundmc 6y ago
I just created a new firebase database for a personal project a couple months ago. They recommend using firestore now, but as far as I can tell there is nothing stopping you from using firebase and it still works fine. This seems to be the type of deprecation he is advocating for. Similarly, there was tooling released to upgrade Cloud SQL versions: > In 2016, we started offering Second Generation instances to Cloud SQL customers. Second Generation instances offer improved performance, availability, and storage capacity. In October, 2018, we released a tool for upgrading First Generation instances to Second Generation. On January 29, 2019, we deprecated First Generation instances in favor of Second Generation. I think maybe Steve's past experiences from within Google are causing him to project the same behaviors onto GCP products, when it doesn't seem to be the case. Though, admittedly I did get bit by the Python 2 issue as well.