3 ms·
This very long article doesn't describe even a single instance of anything GCP has deprecated. It's a long rant with a bunch of f-words, and the claim that he
by crazygringo 6y ago
This very long article doesn't describe even a single instance of anything GCP has deprecated.
It's a long rant with a bunch of f-words, and the claim that he gets deprecation e-mails "about once a month".
Can someone who is informed point to actual GCP services that have been, or are being, deprecated?
From the article, I have no idea whatsoever if this is some huge actual problem with core services... or pulling support for ancient versions of Linux... or sunsetting experimental/beta services that never had guarantees to begin with.
I'd find it pretty surprising for a platform as relatively new as GCP to already be deprecating anything meaningful, so I'd really appreciate if anyone has actual facts here.
(Also I know a lot of people who use GCP, and I've never heard anyone complaining about services being deprecated, so to hear someone complaining about it happening monthly is pretty surprising.)
- mplanchard 6y agoCan’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 agoI 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.
- mtlynch 6y agoPython2 on AppEngine is a huge, painful Google GCP deprecation. I have a friend who built an AppEngine app within the first year of the platform's release, and he's spent the better part of the past 9 months doing almost nothing but managing his company's migration to Python3 AppEngine. It wasn't just migrating from Python2 to Python3 syntax. Google used it as an opportunity to also turn down tons of APIs and services they no longer felt like maintaining. One big difference was the Users API. Python2 AppEngine had a pretty simple way to authenticate users that you could set up in an hour.[0] In Python3, they've dumped that entirely and tell you that you have to move to a totally different solution, and they offer no help with that migration.[1] In Python2 AppEngine, you essentially got a memcache for free. The ndb library[2] allowed applications to read/write to Cloud Datastore, but it also automagically managed the cache for you so that you didn't have to set up a separate cache service. In Python3, they've dumped that and force you to maintain your own cache service and handle all the caching logic yourself.[3] It looks like the ndb library is pretty complete at this point,[4] but when I was looking at a migration earlier this year, the ndb library wasn't even out of beta. Meanwhile, they were breathing down their customers' necks about moving off the Python2 version. I had a fairly small (~8 KLOC) Python2 AppEngine app that I wrote in 2018, but when I realized how much of a hassle it would be to migrate to Python3, I just rewrote it using Gridsome and moved off of AppEngine entirely.[5] [0] https://cloud.google.com/appengine/docs/standard/python/users https://cloud.google.com/appengine/docs/standard/python/user... [1] https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services#user_authentication https://cloud.google.com/appengine/docs/standard/python/migr... [2] https://cloud.google.com/appengine/docs/standard/python/ndb https://cloud.google.com/appengine/docs/standard/python/ndb [3] https://cloud.google.com/appengine/docs/standard/python3/migrating-to-cloud-ndb#caching https://cloud.google.com/appengine/docs/standard/python3/mig... [4] https://googleapis.dev/python/python-ndb/latest/index.html https://googleapis.dev/python/python-ndb/latest/index.html [5] https://whatgotdone.com/michael/2020-04-17 https://whatgotdone.com/michael/2020-04-17
- AnssiH 6y agoBut Python 2 on App Engine is not officially deprecated yet (e.g. not listed here: https://cloud.google.com/appengine/docs/deprecations https://cloud.google.com/appengine/docs/deprecations) and they have not sent the "[Action Required]" email (of which OP talks about) for that yet, so I'm not sure it counts. They are "just" recommending migration. I have a ~60 KLOC AppEngine Python 2 app (started in 2011), but I'll probably migrate that over only when the deprecation actually occurs, as: - that gives the python-ndb library more time to mature (performance and bugs), - easier migration paths for some of the non-py3 services I use (e.g. Images, Users, Memcache) might appear when deprecation actually occurs, either from Google or 3rd parties, - I'm in no hurry, - I will be surprised if Google gives less than 1 year of deprecation notice (Python 2.5 got 4 years from deprecation to termination). (If the APIs I use were available for py3, I would've probably already migrated.)
- nojvek 6y agoFrom what I can remember Datastore-> Firestore (and firestore is a PITA because you can only have one per project even though when interacting with apis you pass in a database name. Go figure) Remote build execution - deprecated. Our live systems went down because of it and they didn’t even send an email they were killing it. Some person just pressed the kill switch and even support was unaware. Their gcloud stuff asks for upgrades all the time. Older gcloud sometimes breaks. Sometimes upgrading to newer gcloud breaks existing code that interfaces with it. It’s not that bad, but yeah GCP doesn’t give a shit a bit backwards compat as the other players do. You get the feeling, they don’t dogfood their own shit. Like their pricing calculator is unusable on iOS. It baffles me that their support says “there is a feedback button” but there is no feedback button. They seem to only care about chrome with their cloud.google.com interface. It really makes me think “what were they thinking?”
- novaleaf 6y agofyi, I use cloud datastore, and there was a breaking change about 2 years ago going from beta to "release", but that's it. You don't need to upgrade your current datastore to firestore, at least I haven't got any "it will break" emails about it. However, I do generally agree about the rant. While datastore still works, I can't upgrade my node-js app because the newer node bindings for GCP break the api's, and I can't upgrade my app's Node version either because They decided to ship static WebRTC binaries for the node GCP packages and those arn't avaiable for node 12.x (for the old package version I'm using)
- NBJack 6y agoIt's more than just GCP. It seems to be a general Google mindset. https://killedbygoogle.com/ https://killedbygoogle.com/
- tqkxzugoaupvwqr 6y agoGoogle AppEngine recently stopped support for Go 1.9. My app ran for four years without my attention which was great. But I also didn’t want to give it any more attention. So Google pulled the plug after I didn’t upload a recompiled version. Yes, they gave half a year notice or so, but I really didn’t feel like crawling for the source code and re-compiling it just to satisfy some Google internal deprecation. When the time came, I redirected my users to my new app that is similar (and hosted on a 4€ Hetzner Cloud instance that I fully control).