5 ms·

Functions are going beta this week

by fidget 10y ago

Moru 10y ago
And discontinued next year?
- deleted 10y ago
  [deleted]
- benley 10y ago
  The standard "lol google will kill it in 6 months anyway" troll doesn't really apply to Google Cloud services. They know better than to be fickle with infrastructure offerings.
  - Moru 10y ago
    No trolling, just tired of setting up things that just stop working and forcing me to work on a fix. I dont work for a big company with a dev team of 20 people, its just me and customer support. Im close to a burn out as it is, I dont need help with it.
    - fidget 10y ago
      They have a minimum of 1 year deprecation policy in their terms of service.
    - ChristianBach 10y ago
      I hear you, discontinuing products that you're dependent on is painful, but discontinuing services that you built your infrastructure around is an outright killer.
    - foxylad 10y ago
      I've used Appengine since 2009. Early on they deprecated the original master-slave datastore, but apart from that I've had zero refactoring around their services. Other services are a different story - from my perspective Google are better at supporting legacy interfaces than most.
      - iampims 10y ago
        They deprecated their alpha search api 2 years in iirc
  - beambot 10y ago
    Counterpoint from an email I received just last week (Feb 21st): > We are writing to inform you that we are winding down sales and renewals of Google Site Search (GSS). Starting April 1st, 2017, new purchases and renewals of GSS will not be available.
    - kyrra 10y ago
      GSS isn't under Cloud and doesn't have the same deprecation policy. Cloud explicitly states that it has a minimum 1-year turndown on any feature they disable.
      - beambot 10y ago
        > They know better than to be fickle with infrastructure offerings Site Search seems like an infra offering to me.
      - inimino 10y ago
        Cloud is still competing with on premises solutions, right? One year is nothing, try ten or twenty.
        newjersey 10y ago
        > Cloud is still competing with on premises solutions, right? One year is nothing, try ten or twenty. Not an expert by any means but I would put more weight to Google's ONE year promise over (to give an example) HPE's twenty years promise. I know it is a cheap shot because I am pretty sure HPE will be bought and sold at least once in the next twenty years.
        xchaotic 10y ago
        FWIW I am now dealing with a system that is supported by HPE for over 10 years now. Even if they get bought out, someone will inherit those support obligations. I am also in the camp of not trusting Google with anything.
      - 10y ago
  - imron 10y ago
    > doesn't really apply to Google Cloud services It might not, but doing it so much for other services destroys trust across the entire brand.
  - ExactoKnight 10y ago
    They did it to their Google Analytics API. We spent four months building a dashboard off of it then Google fucking deprecated it. Thanks Google.
  - ExactoKnight 10y ago
    They did it to their Google Analytics API. We spent four months building a dashboard off of it then Google fucking deprecated it. Thanks Google.
  - themihai 10y ago
    Are you sure? Have you used appengine or any of their cloud libraries? Just found out that some of the services I wrote 3 years ago don't work anymore due various breaking changes. It also very much applies to cloud services themselves! What happened to the email service(appengine powered)?I'm telling you: it no longer exists! Compare that with AWS SES which gets better and better. I could go on and on all day long. Google cloud is nice on paper but fails in practice. If you consider the lock-in it is not worth it on paper either
    - davidjnelson 10y ago
      That happened to me and my sites were down for four months. I lost 15 years of seo, and $30/mo revenue... They just shut down the Python app engine sites with no notice. I'll never use google cloud.
      - scrollaway 10y ago
        What? That sounds like nonsense. Some sources please.
        davidjnelson 10y ago
        I wish it were. It was an enormous amount of effort to get my pagerank that high. I suppose I could post my google analytics before and after, but that's not really data I share with the public.
        scrollaway 10y ago
        I'm not doubting your site was "down for four months". I'm doubting the part where you said "They just shut down the Python app engine sites with no notice". Most notably, I know many people who run these types of sites and outside of GAE being mediocre, I've never heard them complain about anything like that.
        davidjnelson 10y ago
  - anotherturn 10y ago
    Not entirely true. App engine depreciations happen all the time and they give about 1 years notice. Most recently the channel api, before that prospective search, backends, etc etc
    - benley 10y ago
      "oh no I only have _an entire year_ to deal with an API deprecation what ever will I do?" :-P
      - bartread 10y ago
        Well, if it's something you've built your entire offering around it could be a simple fix, or it could be months of work, and that will vary by project. Bear in mind that this is completely non-value-adding work that you didn't plan on just to bring your project back to a functioning state. I.e., some douchebag who has no interest or stake in what you do has just dumped a potentially substantial amount of technical debt into your product backlog and, quite possibly, prioritised it all the way to the top. As somebody else noted above: I don't need people creating more work from me. I can do that quite well enough on my own, thanks very much, and for side-projects this kind of chopping and changing is a pain in the ass. By definition, with side-projects time is limited, so you absolutely have to focus on the most valuable activities to the exclusion of all else. For this reason, I only consider AWS and Azure for my projects: Google are just too fickle. Lucky you, if you have the time to deal with their nonsense. (Btw, I'm not dissing Google on a technical level - they obviously do great, interesting work, and they're certainly one of the pioneers of PaaS. I just don't need the hassle of having to fix stuff because they keep killing APIs, projects, services.)
        anotherturn 10y ago
        Yes exactly. The app specifically affected by Channels API depreciation is a side project that serves a few thousand people. It marches along perfectly well, and I pay Google money for it each month - though the project itself makes no money. Now, I need to consider whether the shift from Channel API to Firebase (and the few days work it'll take to do) is worth the investment, or if I should just shut it down.

Functions are going beta this week

by fidget 10y ago

Functions are going beta this week

Moru 10y ago

And discontinued next year?

deleted 10y ago
[deleted]
benley 10y ago
The standard "lol google will kill it in 6 months anyway" troll doesn't really apply to Google Cloud services. They know better than to be fickle with infrastructure offerings.
- Moru 10y ago
  No trolling, just tired of setting up things that just stop working and forcing me to work on a fix. I dont work for a big company with a dev team of 20 people, its just me and customer support. Im close to a burn out as it is, I dont need help with it.
  - fidget 10y ago
    They have a minimum of 1 year deprecation policy in their terms of service.
  - ChristianBach 10y ago
    I hear you, discontinuing products that you're dependent on is painful, but discontinuing services that you built your infrastructure around is an outright killer.
  - foxylad 10y ago
    I've used Appengine since 2009. Early on they deprecated the original master-slave datastore, but apart from that I've had zero refactoring around their services. Other services are a different story - from my perspective Google are better at supporting legacy interfaces than most.
    - iampims 10y ago
      They deprecated their alpha search api 2 years in iirc
- beambot 10y ago
  Counterpoint from an email I received just last week (Feb 21st): > We are writing to inform you that we are winding down sales and renewals of Google Site Search (GSS). Starting April 1st, 2017, new purchases and renewals of GSS will not be available.
  - kyrra 10y ago
    GSS isn't under Cloud and doesn't have the same deprecation policy. Cloud explicitly states that it has a minimum 1-year turndown on any feature they disable.
    - beambot 10y ago
      > They know better than to be fickle with infrastructure offerings Site Search seems like an infra offering to me.
    - inimino 10y ago
      Cloud is still competing with on premises solutions, right? One year is nothing, try ten or twenty.
      - newjersey 10y ago
        > Cloud is still competing with on premises solutions, right? One year is nothing, try ten or twenty. Not an expert by any means but I would put more weight to Google's ONE year promise over (to give an example) HPE's twenty years promise. I know it is a cheap shot because I am pretty sure HPE will be bought and sold at least once in the next twenty years.
        xchaotic 10y ago
        FWIW I am now dealing with a system that is supported by HPE for over 10 years now. Even if they get bought out, someone will inherit those support obligations. I am also in the camp of not trusting Google with anything.
    - 10y ago
- imron 10y ago
  > doesn't really apply to Google Cloud services It might not, but doing it so much for other services destroys trust across the entire brand.
- ExactoKnight 10y ago
  They did it to their Google Analytics API. We spent four months building a dashboard off of it then Google fucking deprecated it. Thanks Google.
- ExactoKnight 10y ago
  They did it to their Google Analytics API. We spent four months building a dashboard off of it then Google fucking deprecated it. Thanks Google.
- themihai 10y ago
  Are you sure? Have you used appengine or any of their cloud libraries? Just found out that some of the services I wrote 3 years ago don't work anymore due various breaking changes. It also very much applies to cloud services themselves! What happened to the email service(appengine powered)?I'm telling you: it no longer exists! Compare that with AWS SES which gets better and better. I could go on and on all day long. Google cloud is nice on paper but fails in practice. If you consider the lock-in it is not worth it on paper either
  - davidjnelson 10y ago
    That happened to me and my sites were down for four months. I lost 15 years of seo, and $30/mo revenue... They just shut down the Python app engine sites with no notice. I'll never use google cloud.
    - scrollaway 10y ago
      What? That sounds like nonsense. Some sources please.
      - davidjnelson 10y ago
        I wish it were. It was an enormous amount of effort to get my pagerank that high. I suppose I could post my google analytics before and after, but that's not really data I share with the public.
        scrollaway 10y ago
        I'm not doubting your site was "down for four months". I'm doubting the part where you said "They just shut down the Python app engine sites with no notice". Most notably, I know many people who run these types of sites and outside of GAE being mediocre, I've never heard them complain about anything like that.
        davidjnelson 10y ago
- anotherturn 10y ago
  Not entirely true. App engine depreciations happen all the time and they give about 1 years notice. Most recently the channel api, before that prospective search, backends, etc etc
  - benley 10y ago
    "oh no I only have _an entire year_ to deal with an API deprecation what ever will I do?" :-P
    - bartread 10y ago
      Well, if it's something you've built your entire offering around it could be a simple fix, or it could be months of work, and that will vary by project. Bear in mind that this is completely non-value-adding work that you didn't plan on just to bring your project back to a functioning state. I.e., some douchebag who has no interest or stake in what you do has just dumped a potentially substantial amount of technical debt into your product backlog and, quite possibly, prioritised it all the way to the top. As somebody else noted above: I don't need people creating more work from me. I can do that quite well enough on my own, thanks very much, and for side-projects this kind of chopping and changing is a pain in the ass. By definition, with side-projects time is limited, so you absolutely have to focus on the most valuable activities to the exclusion of all else. For this reason, I only consider AWS and Azure for my projects: Google are just too fickle. Lucky you, if you have the time to deal with their nonsense. (Btw, I'm not dissing Google on a technical level - they obviously do great, interesting work, and they're certainly one of the pioneers of PaaS. I just don't need the hassle of having to fix stuff because they keep killing APIs, projects, services.)
      - anotherturn 10y ago
        Yes exactly. The app specifically affected by Channels API depreciation is a side project that serves a few thousand people. It marches along perfectly well, and I pay Google money for it each month - though the project itself makes no money. Now, I need to consider whether the shift from Channel API to Firebase (and the few days work it'll take to do) is worth the investment, or if I should just shut it down.