News for hackers. Stuff that matters.
Re:Serverless Architectures by stickfigure on Friday June 17, 2016 @10:50AM (#11922949)
By this definition, we've been running "serverless" on Google App Engine for most of a decade.

* 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.

Re:Serverless Architectures by vgt on Friday June 17, 2016 @11:13AM (#11923099)
Oh buzzwords...

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)

Re:Serverless Architectures by gaius on Friday June 17, 2016 @05:58PM (#11925810)
In the 1970s this was called the mainframe bureau...
Re:Serverless Architectures by cbd1984 on Saturday June 18, 2016 @04:19AM (#11927566)
Eh, literally everything can be a buzzword. "Email" has been a buzzword in the past, as has "Internet" and "mobile phone" and so on.
Re:Serverless Architectures by tete on Saturday June 18, 2016 @10:27AM (#11928752)
Eh, no. Actually they weren't. A mobile version of a phone makes as much sense as electronic mail. Cause that is what it is.

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.

Re:Serverless Architectures by osipov on Friday June 17, 2016 @11:07AM (#11923049)
If GAE has had "serverless" for most of a decade, then why did Google decide to create Google Cloud Functions? https://cloud.google.com/functions/docs/
Re:Serverless Architectures by vgt on Friday June 17, 2016 @11:33AM (#11923229)
I think OP's chief argument is that "serverless" is monopolized by AWS Lambda and the like, and probably unfairly.

The answer is that Cloud Functions and AppEngine fulfill different use cases. There's clearly room for both.

Re:Serverless Architectures by osipov on Friday June 17, 2016 @11:51AM (#11923344)
There doesn't appear to be a monopoly on "serverless" and the term has been used by many vendors including IBM at the last Serverless Conference[1].

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)

[1] http://serverlessconf.io/#agenda

Re:Serverless Architectures by hassy on Friday June 17, 2016 @01:38PM (#11924159)
Because Lambda/Cloud functions are meant for scripting tasks in your cloud environment, not for building full-fledged apps.

(Lambdas couldn't even be triggered with HTTP calls when AWS Lambda launched.)

Re:Serverless Architectures by madeofpalk on Saturday June 18, 2016 @12:07AM (#11927057)
Yes.

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.

Re:Serverless Architectures by vikeri on Friday June 17, 2016 @04:35PM (#11925382)
I spoke to a solutions architect on AWS who said that their recommendation for building a new backend service (eg. a REST API) is to use API gateway and Lambda. I definitely got the impression that he meant full-fledged apps.
Re:Serverless Architectures by zippergz on Friday June 17, 2016 @08:01PM (#11926280)
I have done some (small-ish) projects with API Gateway and Lambda. Lambda itself is pretty nice. The API Gateway is a pain, and has a lot of rough edges. Especially if you need to do anything other than standard JSON in and out. I’ve spent way more time than I’d like to admit futzing with mapping templates and models to try to get stuff to work the right way. And then dealing with errors from the Lambda function in a sensible way is a headache all its own.

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.

Re:Serverless Architectures by nickbauman on Friday June 17, 2016 @06:03PM (#11925830)
I did this. AppEngine is a far more cohesive and polished service than cobbling together Lambda, S3, API Gateway, SQS and Dynamo (which you'd need to do to actually have a fully functioning site).
Re:Serverless Architectures by orasis on Friday June 17, 2016 @03:03PM (#11924833)
I'm building a full fledged app. http://blog.improve.ai/ Once there is an Express type framework on top of Lambda and API Gateway, it will be a natural development model.
Re:Serverless Architectures by osipov on Friday June 17, 2016 @02:11PM (#11924403)
Here's how Google defines Cloud Functions: "Lightweight Event-based Microservices".

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?

Re:Serverless Architectures by nathankunicki on Friday June 17, 2016 @02:57PM (#11924792)
He is correct though, it's even in the sentence you quoted:

"...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.

Re:Serverless Architectures by daxorid on Friday June 17, 2016 @11:26AM (#11923187)
Functions looks interesting, but only supports node.js. GAE has the advantage that it support multiple language targets.
Re:Serverless Architectures by nickbauman on Friday June 17, 2016 @06:00PM (#11925818)
Cloud Functions are just the functions. Gae is that and more.
Re:Serverless Architectures by bpicolo on Friday June 17, 2016 @11:29AM (#11923200)
I've been using Elastic Beanstalk lately and it's a true pleasure.
Re:Serverless Architectures by epalmer on Friday June 17, 2016 @11:37AM (#11923260)
Curious about your use of beanstalk:

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

Re:Serverless Architectures by pilom on Friday June 17, 2016 @12:00PM (#11923409)
Beanstalk doesn't like having more than one virtual host per application/server/load balancer. You can do it but its a lot of custom code to make it work. Beanstalk does do deploys very well though with automatic deploys to a subset of instances, checking they are working, then deploying to a new set of instances. Big fan but it is really designed for one domain per instance set.
Re:Serverless Architectures by bpicolo on Friday June 17, 2016 @11:41AM (#11923279)
Beanstalk handles the load balancing for you and throws a DNS entry in front of it all, as far as I can tell. Works well so far. It's smart and (seems to do) blue/green style deploys for my single app instance atm I believe.

(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).

Re:Serverless Architectures by Illniyar on Saturday June 18, 2016 @03:25AM (#11927456)
If you are referring to the definition of "FAAS" as described in the article, then no, GAE is not serverless (or FAAS) because it is not stateless (though you may use it as such) it can keep things in memory, such as a local sesion cache (from what I recall), though you probably shouldnt rely on it as such.
Re:Serverless Architectures by tianlins on Friday June 17, 2016 @12:15PM (#11923513)
I think one difference is that for many languages like Python, the http endpoints are hosted in one process. That's less horizontally scalable than lambda services.
Re:Serverless Architectures by takeda on Friday June 17, 2016 @09:02PM (#11926487)
I'm not sure where you got this from. There's nothing inherent in WSGI that prevents you from spawning multiple threads and processes. I'm unaware of WSGI implementation that does not do this. uWSGI even shows how to do this even in their quickstart [1].

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...

Re:Serverless Architectures by icebraining on Friday June 17, 2016 @01:07PM (#11923847)
Why? Production-ready application servers like uwsgi can run multiple processes and distribute requests between them.