Hacker News Reader

Comment by Fredej | Hacker News Reader

As someone who's always late to the party on these things (I just picked up Docker this year! Yay!) this seems like exactly what I've been missing when trying to pick up serverless.

Granted I haven't really tried building anything yet, but part of that is that I needed a way to get an overview what could even be done. This seems like a nice way to get introduced.

View on HN

Serverless is fantastic for event-driven workloads at arbitrary scale. There are definitely some things to learn about serverless runtimes, but beyond that there isn't much complexity aside from the large hill to climb which is understanding IAM.

Here are a lot more examples: https://github.com/serverless/examples

And if you'd rather define the infrastructure side as code vs YAML, you might want to check out Pulumi as well: https://github.com/pulumi/examples

>> if you'd rather define the infrastructure side as code vs YAML

Or AWS CDK

https://aws.amazon.com/cdk/

> arbitrary scale

If you have arbitrary funds.

Point is serverless costs more per unit deliverable

Asymptotically, yes. But if you factor in development time, infrastructure management and security concerns, the point where serverless really "costs more" may be very high indeed.

I would love to hear the argument that serverless impacts cost of security concerns at all. I'm not warm to the idea that it also impacts development time, but I'd love to hear that argument too.

Reply on news.ycombinator.com