We've been discussing Google BigQuery as serverless lately. It's a nice succinct way of saying "fully-managed" + "no-ops" + "no resource deployment" + "seamless scaling" + "separation of storage and compute" + "deployed regionally" + etc. Some customers talk about BigQuery as "Data Center is the Database". So these buzzword help describe what BigQuery is and how it is different from other analytics services and technologies.
In any case, if a buzzword helps get across some meaning, sure, go for it. Folks just get carried away :)
(work on BigQuery)
It's not like web 2.0 which isn't a newer version and also not like serverless when it has servers or cloud which isn't a cloud.
Btw. this isn't about how new it is. Just look at stuff from the 90s. The terms they also didn't stick.
Also those things had a specific well defined meaning.
Like again web 2.0 didn't. User created content, Ajax, etc. all surround that.
Not saying buzzwords can't become meaningful, but they are still buzzwords.
Also they still are wrong when they are something like serverless, which is just plain wrong.
The answer is that Cloud Functions and AppEngine fulfill different use cases. There's clearly room for both.
There is definitely room for many kinds apps in the PaaS space, including serverless as well as microservices. OP was arguing that existing platforms like GAE have been supporting serverless and can continue to do so. However, the premise of the serverless computing movement is that newer platforms (e.g. OpenWhisk, Google Cloud Functions, AWS Lambda) are better for running serverless applications than traditional PaaSes (e.g. Heroku, Bluemix, OpenShift)
(Lambdas couldn't even be triggered with HTTP calls when AWS Lambda launched.)
I'm a massive fan of AWS Lambda, but using it to serve public API quests is just a nightmare. Just because you _can_ do something, doesn't mean you should.
I'm constantly puzzled by why people use Lambda for this - if you don't want to deal with managing traditional services, there's plenty of other options out there (in AWS and otherwise) that are much more suited to the task of serving a website.
I generally really like AWS and I use it for a ton of stuff, but I very much welcome competition and innovation in this space.
Google Cloud Functions is a lightweight, event-based, asynchronous compute solution that allows you to create small, single-purpose functions that respond to cloud events without the need to manage a server or a runtime environment.
Where is the reference to scripting?
"...single-purpose functions that respond to cloud events..."
They are meant to react to events within your infrastructure, rather than being public facing application endpoints.
I'm considering using beanstalk for a php app but we have content changes that are very frequent. 134 domains (virtual hosts) and maybe 500 pages (the html) change a day.
How do you update the load balanced set of instances when the instances count changes? tks
(I'm only running on a single box so far, mostly using it because it made deploying to production and all the annoyances that come with that a breeze).
Having said that, this is actually irrelevant when trying to scale out. There's nothing that prevents you from starting your application multiple times each copy on a different machine. As long as your application is stateless (which is a requirement no matter which language you use). I don't think there's any programing language which prevents you from doing that.
[1] http://uwsgi-docs.readthedocs.io/en/latest/WSGIquickstart.ht...
* We don't monitor how many instances are running and don't really care. Our "functions" are http endpoints. GAE spins up or down instances to meet the load. Our interface with "instances" is just the size of the bill at the end of the month.
* Async task processing is also just an http endpoint function. We even have a little bit of syntactic sugar so it looks like we're just adding functions to a queue.
* We have no ops or devops staff. We just deploy code that implements functions (http endpoints).
* Persistence is also scaled by Google; there's no database server, just an API to read/write data that scales infinitely (or at least, scales with linearly our bill, not limited by the dataset).
It sounds to me like the article is trying to distinguish between "serverless" and PaaS by describing PaaS done poorly. For the longest time, GAE didn't even expose the # of instances servicing your app. They've exposed a lot more of the underlying constructs since, but you can still ignore them unless you're trying to hyperoptimize your bill.