Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Counterpoint to that though: "Serverless" isn't all that much "easier" to setup compared to traditional server setup. You still need to know how to wireup your request gateway to the correct service, you need to write your app for a serverless setup, setup security groups, etc. None of that is particularly "accessible" for someone trying to get running ASAP.

I agree tech is getting democratised, but when talking about products that allows it, I'm thinking of products like Firebase or the recent darklang, not AWS Lambda. From all the Lambda usage that I've encountered so far, they are still very much in the domain of a "sysadmin".



> "Serverless" isn't all that much "easier" to setup compared to traditional server setup. You still need to know how to wireup your request gateway to the correct service, you need to write your app for a serverless setup, setup security groups, etc.

You only have to setup security groups if you are running lambda's in a VPC, which in the simple case (e.g., not running a cloud extension of an internal corporate network) you probably don't.

https://lumigo.io/blog/to-vpc-or-not-to-vpc-in-aws-lambda/

And, yeah, its a lot simpler than a traditional server setup without that. And even with it.


Agreed, AWS lambda is still (very) scary. To me, serverless is more glitch.com [1] than AWS.

When there is is no infra to deal with, U/DevX becomes much easier. "Remix this" is pure product joy

[1]: https://glitch.com/~mapbox-demo


I've found https://github.com/Miserlou/Zappa to be super useful for simple Lambda deployments. It's only for python, but I am pretty sure you have other solutions for node, ruby...


We use http://apex.run/ but mainly because that’s what we started with and it hasn’t given us a reason to look around yet.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: