News for hackers. Stuff that matters.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by jacob019 on Thursday October 25, 2018 @11:33AM (#18301673)
I cringe every time I read serverless, what exactly is that supposed to convey? That the code is so ephemeral that it doesn't even exist, or does the code execute on a higher plane of existence without the need for lowly hardware and dirty power?

Furthermore, I fail to see what real world problems this architecture solves. It seems to offer rapid horizontal scaling at the cost of complexity, performance, and vendor lock-in.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by jkingsbery on Thursday October 25, 2018 @11:42AM (#18301763)
(Disclaimer: I am an Amazon employee, but my opinions are my own. I don't work in the AWS organization, so my knowledge of AWS services isn't substantially different than other engineers outside of Amazon.)

There obviously are servers, "serverless" just implies you don't own them.

There's a few problems that using serverless solves:

1. It's great for low volume sites or services. You don't need to rent hardware that runs the whole month if you only get pinged a few times per day.

2. It reduces operational burden. A whole class of problem goes away - patching operating systems and application servers.

3. It provides an abstraction layer for processing events. Events could be HTTP requests to a site, data coming in from an IoT device, that a new file was uploaded to S3, etc.

Performance isn't that different from using EC2 (or the non-AWS equivalents), other than cold start times, and choice of language platform can help mitigate that.

In terms of complexity, for the project work I've done the complexity isn't different than running something in any other application server.

Cloud providers other than AWS have a serverless offering, and there are frameworks out there for abstracting the differences, so tooling support doesn't have to come with lock-in. In addition, a well-architected serverless application has a pretty small layer interfacing with the serverless framework, so the code lock in is negligible.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @07:57PM (#18305678)
Performance isn't that different from using EC2 (or the non-AWS equivalents), other than cold start times, and choice of language platform can help mitigate that.

So performance any different except for it’s a huge difference depending on the language, whether it is in VPC forcing the need to create ENIs, etc.

I’m a multi certified AWS true believer and I love lambda for everything else besides APIs, but let’s not ignore the large performance penalty of cold starts and lack of connection pooling.

You really don’t save money over just using a bunch of micro instances behind a Load Balancer and autoscaling. Elastic Beanstalk makes managing it dead simple.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by pavlov on Thursday October 25, 2018 @11:59AM (#18301925)
Already a decade ago there was Google App Engine, which was “serverless” as far as I can tell.

Back then developers were dismayed about the unpredictable cost of App Engine. The same problem remains today with Lambda and others.

Is it just a solution whose time has come now, ten years later? Or is there something else to Lambda that I’m missing?

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by nailer on Thursday October 25, 2018 @12:56PM (#18302370)
GAE was very much the first serverless platform. Cost is very low - most people would make savings most months, but you can set up billing alerts to help you go higher.

Also original GAE was hampered by having a product owner that didn't care about it (at the time I was working on the largest GAE app inside Google). We (as internal customers) ending up writing chunks of the AE SDK to be able to have our apps run reliably.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by int0x80 on Thursday October 25, 2018 @12:00PM (#18301931)
I don't think the 'cold-start' issue should be taken lightly. Yes, some services won't care at all, and you can mitigate it as you say by choosing a particular backend. Yet it is still a big concern for Java for example when you can not use graalvm etc.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by esotericn on Thursday October 25, 2018 @11:54AM (#18301870)
#1 - A VPS that you can run multiple services on is 5 quid a month.

I spent more than that on a single train in to the city today.

Or you can just run from a residential connection for effectively free if your service is _that_ small.

#2 - "Serverless" paradigms change often enough that it's essentially another form of patching.

It's also obviously not true, any system you write code on needs to be patched because it has auth to this system.

#3 seems to be buzzwords with no substance?

As far as I can tell, the only "problem" that "serverless" (i.e. Our Servers) solves is Amazon not monetizing everything ever.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by jnty on Thursday October 25, 2018 @12:21PM (#18302098)
Quoting the price of a VPS totally misses the point - the cost is in finding one, setting it up with an environment somehow, monitoring it, making sure it stays patched and current over years and years...

While you're busy figuring out what monitoring solution to use on your VPS to monitor the running all for the sake of a little Python script, I've already set up a lambda function and maybe set a cloudwatch alarm to look after it and can move on to the next thing and leave it running indefinitely. Depending on the usecase I might not even pay a penny during that time, either.

I swear 90% of the hate for serverless purely stems from irritation at the name.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by isomorph on Thursday November 01, 2018 @05:39PM (#18358732)
Hi - I couldn't find a way to contact you and was unable to reply in situ for some reason. Could you please say more about why you felt I had gratuitously editorialised the title to my latest submission? ( https://news.ycombinator.com/submitted?id=isomorph )

I have checked the definition of the word "editorialise: To present an opinion in the guise of an objective report." - I did not express any opinion in the title - I simply added context for those who don't know about the so-called "contaminated blood scandal" in the UK. Namely the three-letter detail I added was "HIV" i.e. that the UK's government-run National Health Service infected patients as young as 8 years old with HIV.

This change was not gratuitous as it added essential context to the story.

I have checked the Hacker News guidelines and since the article dispels myths people have about health systems, I felt it was pertinent.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @08:06PM (#18305726)
Quoting the price of a VPS totally misses the point - the cost is in finding one, setting it up with an environment somehow, monitoring it, making sure it stays patched and current over years and years...

If you are spending that much time managing infrastructure on AWS, you’re doing it wrong. ElasticBeanstalk makes it dead simple.

While you're busy figuring out what monitoring solution to use on your VPS to monitor the running all for the sake of a little Python script, I've already set up a lambda function and maybe set a cloudwatch alarm to look after it and can move on to the next thing and leave it running indefinitely. Depending on the usecase I might not even pay a penny during that time, either.

And you can do the same with AWS and a bunch of micro instances. But if it’s that low volume, I would just host it myself.

I swear 90% of the hate for serverless purely stems from irritation at the name.

I love serverless for everything but APIs. But 90% of my hate for serverless is with APIs and the cold starts.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by mrfredward on Thursday October 25, 2018 @12:37PM (#18302234)
>Or you can just run from a residential connection for effectively free if your service is _that_ small.

Been there, done that. Buy a raspberry pi, install raspbian, install nginx, node, whatever the stack is gonna be, configure port forwarding on a router, spend hours to days getting it working. Have tons of downtime--oops you don't have a static ip, oops your sd card got corrupted, hey lets update this to the latest version oh no everything is broken...and on and on and on.

Or, figure out how to use S3 buckets and lambda functions once, and from then on watch everything just work and cost virtually nothing. For small (I'm the only user) types of projects, I'll stick to serverless for now on, so I can be a programmer and not a sysadmin.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @08:01PM (#18305705)
Or you can just run from a residential connection for effectively free if your service is _that_ small.

This is very true. I’m an AWS true believer and I use most of the most popular features all of the time for work but for a low volume side project, I would host it on my own computer. I have 900Mbps upload bandwidth. If I were going to use AWS, I would use a cheap LoghtSail instance.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by jk563 on Thursday October 25, 2018 @12:23PM (#18302122)
Why spend $5 when you could spend $1? I've got a site running without using servers and it basically costs the R53 hosted zone cost as it's very low traffic. No servers to configure, no residential connection to potentially fall over, high durability. Why wouldn't I use it?

Different use cases warrant different solutions.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by jolmg on Thursday October 25, 2018 @12:40PM (#18302257)
> Or you can just run from a residential connection for effectively free if your service is _that_ small.

Not gonna be possible soon, now that ISPs are starting to hand out private IPs to customers. That's going to keep happening until the world moves to IPv6.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by tomphoolery on Thursday October 25, 2018 @11:48AM (#18301831)
I'm just waiting for "Serverless" to not mean "app-less" or "organization-less"...
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by oogali on Thursday October 25, 2018 @01:31PM (#18302672)
I struggle with trying to understand how serverless is radically different in concepts than old-school cgi-bin.

In both scenarios, you don't necessarily own the servers.

Best practice dictates that your static content lives in a separate area rather than within your application (a different directory or alias, or in the serverless context: an S3 bucket)

You don't worry about patching upstream OSes or applications.

You front your application and static content with an "API gateway" (or in the cgi-bin case: Apache httpd w/mod_rewrite).

Your application's implementation is governed by whatever interpreters are available to you (#!/usr/bin/perl vs. #!/usr/bin/python vs. Node from a drop-down)

Any environment specifics are injected into your application's operating context (environment variables in the case of cgi-bin, or an argument to your entry function in the case of AWS Lambda).

The one radical difference I do recognize is the independent-ish execution environment: e.g. my CPAN modules, don't intermix with your CPAN modules.

It seems like the same paradigm, but with a new coat of paint.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by scarface74 on Thursday October 25, 2018 @07:51PM (#18305642)
I cringe every time I read serverless, what exactly is that supposed to convey? That the code is so ephemeral that it doesn't even exist, or does the code execute on a higher plane of existence without the need for lowly hardware and dirty power?

Why every time someone mentions “serverless”, there is a post where people feign ignorance and “cringes”. Do you also cringe when people mention that there is a virus on their computer or a bug in their program? Words change meanings over time. From your post, you obviously know what serverless means in context.

Furthermore, I fail to see what real world problems this architecture solves. It seems to offer rapid horizontal scaling at the cost of complexity, performance, and vendor lock-in.

Any complex system you always have “vendor lock-in”. It’s just like all of the coders who have the nice pretty Repository Pattern just in case their business decides to rip out their multi million dollar Oracle installation.

Furthermore, I fail to see what real world problems this architecture solves. It seems to offer rapid horizontal scaling at the cost of complexity, performance, and vendor lock-in.

Lambdas are not just for APIs and it’s the one use case that I avoid using it for. I use it mostly to respond to events and stream processing with Kinesis.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by dustingetz on Thursday October 25, 2018 @11:56AM (#18301890)
Serverless (to me) means userland code is just functions. It is very simple. It may actually reduce lockin, because simple functions can port to any platform, even servers! (You just call the function)

I co-made http://www.hyperfiddle.net/ , which can do 100% serverless websites in two easy steps: 1) type in markdown or clojurescript, 2) click save.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by lostcolony on Thursday October 25, 2018 @12:09PM (#18301994)
I'll give you one where it benefits us, in the real world, where it's -not- just horizontal scalability.

Almost all of my team's efforts are internal applications. They're high throughput ad related functionalities, but fundamentally another business client says "hey, we have a user, we need an ad", and all our stuff works to fill it.

We are, as such, on an internal VPC in AWS. This is fine.

But we sometimes need to allow for client code run outside of the network to be able to securely change out our stuff; think ad partners modifying their inventory.

We can add an API on top of one of our services, but then we have to deal with authentication and proxying.

We can certainly authenticate and proxy those requests into the network ourselves. But that creates some fun and interesting risks and issues; we're building something explicitly to bypass the safeguards of running in a private subnet in our own VPC, and tunnel traffic from the big wide world into the depths of our own network (which is also connected to our corporate network).

We can also spin up a new service on a server that lives outside the VPC; however that has the downside that we're paying for an instance for a very low traffic service, and it still requires support.

Or, we use a Serverless paradigm. The website hits API Gateway/lambda endpoints, authentication is provided via Cognito, and it all leads to the lambda executing against a single resource (S3, Dynamo, whatever) to modify data that our services read from. No entering our network, and all security relying on security primitives Amazon owns and maintains (they are far better equipped to handle it than we are). And it will cost us pennies, while leaving our existing infrastructure unaffected.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by kentm on Thursday October 25, 2018 @11:40AM (#18301741)
I think the first point of your rant is that it’s a misonomer and that’s correct. There’s still a server there. “Serverless” means that you don’t think about or manage individual servers yourself and let your provider abstract it away from you.

You mostly understand the trade offs. The advantages are reduced ops in the happy case and modeling your software in a way that is amenable to horizontal scaling. Providers make executing the horizontal scaling pretty easy for the typical case. The disadvantages are vendor lock in the inability to do real deep diving if you have a problem with the hosting stack rather than the service logic itself.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by watty on Thursday October 25, 2018 @11:43AM (#18301764)
The idea is to reduce complexity as developers can simply provide code and let the service handle everything else.

Unfortunately, the technology isn't there yet and serverless is actually more complex than traditional managing servers.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by all_blue_chucks on Thursday October 25, 2018 @12:18PM (#18302064)
As a security person I love serverless. Sometimes getting people to patch or harden servers can be like pulling teeth. These problems just go away in a serverless arc.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by stephengillie on Thursday October 25, 2018 @12:09PM (#18301998)
Old-school serverless is a flat HTML page served by a simple host over HTTP. These days, S3 is robust enough to be the simple host.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by mitchtbaum on Thursday October 25, 2018 @01:52PM (#18302903)
I think the term they're skirting is "hosted".

For "serverless", I think of users downloading the whole application and running it locally. To do that, the code, content, and config need to be made portable and reusable, ie packaged.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by duxup on Thursday October 25, 2018 @11:35AM (#18301690)
I just think of it as "There is some layer of software that you don't have to think about anymore because we handle it."

That could mean ANYTHING, and result in ANYTHING, but ... it's usually what it means.

Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by msoad on Thursday October 25, 2018 @11:59AM (#18301918)
Just like how the cloud is "hardwareless" functions are serverless.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by mavdi on Thursday October 25, 2018 @11:35AM (#18301698)
Shhhhh... bread and butter... it's just a way for us to make shit up and charge corps for failed application rewrites that are google scale from the start for their 10 customers.
Re:Build a 100% Serverless Website with AWS in 7 Easy Steps by MuppetMaster42 on Thursday October 25, 2018 @08:54PM (#18305939)
I used to work at a startup which transitioned to lambda from ec2.

We rewrote our backend from rest php to graphql typescript.

I can tell you that it is amazing operationally. You push code to aws and it just runs.

A comparison with manually managed ec2:

- push code to lambda and lambda automatically handles the dns updates and VIP swaps. No need to worry about configuring multi region blue-green deployments and health checks.

- no chance of a server needing manual intervention because of an errored state - because you can't store state between requests (not entirely true, but true enough). But failing that you know that the container will die soon anyways.

- automatic scaling instantly. Our platform was b2b, so most of the traffic was 7-7. Instead of running load balancers and scaling the servers, we needed to do nothing. AWS starts and kills new instances to handle the load automatically.

- no need to worry about the server config. Only need to specify a node version and a CPU size. It's a godsend from a dev standpoint because ultimately you don't care about that. Why bother managing the OS config, drivers, installed software + libraries. Sure it me as you can't squeeze every cycle of perf out a box, but chances are you aren't in a position to need to.

- pay per call, not per second. We were serving hundreds of thousands of calls via lambda every month, and the bill came out just over a single digit. I've read articles about the crossover point cost wise but it takes some decent scale to get there.

Theres no rules about how you architect a lambda function, just rules about how long it runs for.

Like I said, we ran our entire graphql api via a single lambda function and it worked great.

Things get a little more complicated when you need to kick off background processes, but again that can be pretty simple if you want it to be.

We just pushed messages to an sns queue which triggered a different lambda off. Note though that all this code was in the same repo, sharing code within everything.

The tldr of this really is: imagine running a service was as simple as pushing code to aws. That is what lambda enables.