5 ms·

Of course, the downside to doing anything with a Google product is that it could be deprecated next year...

by remmargorp64 7y ago

inscrutable 7y ago
except it's open source...
- akoncius 7y ago
  please give a link to source
  - foolinaround 7y ago
    its more an adherence to open standards - it is built on knative
  - wstrange 7y ago
    https://github.com/knative https://github.com/knative https://github.com/google/gvisor https://github.com/google/gvisor
dangoor 7y ago
Assuming you’re using SQL or something else that’s portable for your data, the app is just a standard app in a container. It would be easy to move elsewhere, or even to just deploy to a different Google Cloud service.
tpetry 7y ago
It‘s slready like a meme: the typical comment on the google cloud that it could be closed tomorrow. When will everyone understand that google cloud (money earning product) is different to all the other free products
- xenospn 7y ago
  Burden of proof is on Google.
- llampx 7y ago
  Money-earning products have been shut down at Google before.
- gumby 7y ago
  > When will everyone understand that google cloud (money earning product) is different to all the other free products When Google demonstrates it. They've already discontinued various parts of their cloud product. True, they are unlikely to shut down gmail, search, or Android. On the other hand google's cloud is a money loser that has slipped to a distant #4 in the cloud rankings. But like many of Google's revenue-generating products it exists to show Wall Street that they have an increasingly diversified revenue stream (I think advertising is "down" to around 87%). They have lots of bets to try an improve this but little to show for it. They did recently commit $2B to making GCP a player but I suspect that if that doesn't show results by the end of 2020, investment in this sector will fall precipitously.
  - tpetry 7y ago
    Do you have examples of discontinued Google Cloud Platform products?
    - libria 7y ago
      https://cloud.google.com/prediction/ https://cloud.google.com/prediction/
    - gumby 7y ago
      You don't need to ask me: Google provides their own handy list of examples (some like messaging API show up under other names like XMPP; others don't appear on this list because they were marketed differently, e.g. Google Print): https://cloud.google.com/appengine/docs/deprecations/ https://cloud.google.com/appengine/docs/deprecations/
      - dodobirdlord 7y ago
        Many of those seem to have been around for well more than the 1 year deprecation minimum, and most of them appear to be some combination of Alpha/Beta products or language runtimes. Alpha/Beta products aren't really on-topic, and the language runtime stuff doesn't look all that different from how AWS does runtime deprecations. https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html https://docs.aws.amazon.com/lambda/latest/dg/runtime-support...
lallysingh 7y ago
Can we standardize this standard comment? Say a URL that points to the problems we always see complaints about for using a Google service? Then someone posts that link at every Google HN post and we can all get on with our lives? They're boilerplate and don't add to the discussion.
- rantwasp 7y ago
  i suggest a TLA in the title so that we all know what is going to happen. why wast a good comment on it
- GordonS 7y ago
  Yes, as much as I agree with the sentiment of the GP, these comments really are just a bore now.
yegle 7y ago
Disclaimer: I work on Cloud Run as an SRE. Google Cloud has an official deprecation policy. If a product is labeled GA, Google Cloud guarantees that the service will continue running for at least 12 months since the announcement of deprecation.
- OkGoDoIt 7y ago
  Exactly. According to what you said, any service with that policy could literally shut down next year if there is a deprecation announcement this year. Which is better than some small no name startup service provider who might just go out of business tomorrow, but among all the big cloud providers Google is definitely the hardest to trust with longevity. A more realistic concern is that Google might substantially change the free tier making this more expensive, or might shut down some auxiliary product that would be painful to switch from without migrating clouds completely, or that a payment might bounce for some reason and now I’m locked out of all of my google services without recourse. Sure the odds of all of the above are relatively low, but from what I’ve seen they are a lot higher on Google than they are on Azure or AWS.
  - yegle 7y ago
    That 12 months is the minimum guaranteed period that your service won't be interrupted. See the full list of deprecations in App Engine: https://cloud.google.com/appengine/docs/deprecations/ https://cloud.google.com/appengine/docs/deprecations/ High profile deprecations are handled carefully and we usually handle them with extended deprecation period with clear migration path/doc and communications. Notable examples in the table: 1. Python 2.5: 4+ years 2. Java 6: 20 months with existing user automigrate to Java 7 3. Java 7: 13 months with existing user automigrate to Java 8 4. Master/slave datastore: 3+ years. Considering App Engine is the first Google Cloud offering, I'd say we have a very good track record of meet our deprecation policy and usually exceeds it.

Of course, the downside to doing anything with a Google product is that it could be deprecated next year...

inscrutable 7y ago

except it's open source...

akoncius 7y ago
please give a link to source
- foolinaround 7y ago
  its more an adherence to open standards - it is built on knative
- wstrange 7y ago
  https://github.com/knative https://github.com/knative https://github.com/google/gvisor https://github.com/google/gvisor

dangoor 7y ago

Assuming you’re using SQL or something else that’s portable for your data, the app is just a standard app in a container. It would be easy to move elsewhere, or even to just deploy to a different Google Cloud service.

tpetry 7y ago

It‘s slready like a meme: the typical comment on the google cloud that it could be closed tomorrow. When will everyone understand that google cloud (money earning product) is different to all the other free products

xenospn 7y ago
Burden of proof is on Google.
llampx 7y ago
Money-earning products have been shut down at Google before.
gumby 7y ago
> When will everyone understand that google cloud (money earning product) is different to all the other free products When Google demonstrates it. They've already discontinued various parts of their cloud product. True, they are unlikely to shut down gmail, search, or Android. On the other hand google's cloud is a money loser that has slipped to a distant #4 in the cloud rankings. But like many of Google's revenue-generating products it exists to show Wall Street that they have an increasingly diversified revenue stream (I think advertising is "down" to around 87%). They have lots of bets to try an improve this but little to show for it. They did recently commit $2B to making GCP a player but I suspect that if that doesn't show results by the end of 2020, investment in this sector will fall precipitously.
- tpetry 7y ago
  Do you have examples of discontinued Google Cloud Platform products?
  - libria 7y ago
    https://cloud.google.com/prediction/ https://cloud.google.com/prediction/
  - gumby 7y ago
    You don't need to ask me: Google provides their own handy list of examples (some like messaging API show up under other names like XMPP; others don't appear on this list because they were marketed differently, e.g. Google Print): https://cloud.google.com/appengine/docs/deprecations/ https://cloud.google.com/appengine/docs/deprecations/
    - dodobirdlord 7y ago
      Many of those seem to have been around for well more than the 1 year deprecation minimum, and most of them appear to be some combination of Alpha/Beta products or language runtimes. Alpha/Beta products aren't really on-topic, and the language runtime stuff doesn't look all that different from how AWS does runtime deprecations. https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html https://docs.aws.amazon.com/lambda/latest/dg/runtime-support...

lallysingh 7y ago

Can we standardize this standard comment? Say a URL that points to the problems we always see complaints about for using a Google service? Then someone posts that link at every Google HN post and we can all get on with our lives? They're boilerplate and don't add to the discussion.

rantwasp 7y ago
i suggest a TLA in the title so that we all know what is going to happen. why wast a good comment on it
GordonS 7y ago
Yes, as much as I agree with the sentiment of the GP, these comments really are just a bore now.

yegle 7y ago

Disclaimer: I work on Cloud Run as an SRE. Google Cloud has an official deprecation policy. If a product is labeled GA, Google Cloud guarantees that the service will continue running for at least 12 months since the announcement of deprecation.

OkGoDoIt 7y ago
Exactly. According to what you said, any service with that policy could literally shut down next year if there is a deprecation announcement this year. Which is better than some small no name startup service provider who might just go out of business tomorrow, but among all the big cloud providers Google is definitely the hardest to trust with longevity. A more realistic concern is that Google might substantially change the free tier making this more expensive, or might shut down some auxiliary product that would be painful to switch from without migrating clouds completely, or that a payment might bounce for some reason and now I’m locked out of all of my google services without recourse. Sure the odds of all of the above are relatively low, but from what I’ve seen they are a lot higher on Google than they are on Azure or AWS.
- yegle 7y ago
  That 12 months is the minimum guaranteed period that your service won't be interrupted. See the full list of deprecations in App Engine: https://cloud.google.com/appengine/docs/deprecations/ https://cloud.google.com/appengine/docs/deprecations/ High profile deprecations are handled carefully and we usually handle them with extended deprecation period with clear migration path/doc and communications. Notable examples in the table: 1. Python 2.5: 4+ years 2. Java 6: 20 months with existing user automigrate to Java 7 3. Java 7: 13 months with existing user automigrate to Java 8 4. Master/slave datastore: 3+ years. Considering App Engine is the first Google Cloud offering, I'd say we have a very good track record of meet our deprecation policy and usually exceeds it.