3 ms·

I think I fail to understand how Lambda works better for startups. I see primarily 2 arguments. The first one is simplicity. You pack your Node.js application,

I think I fail to understand how Lambda works better for startups. I see primarily 2 arguments. The first one is simplicity. You pack your Node.js application, upload to lambda and it works. But then in the article I see a chart with API Gateway, then Lambda, then SNS and then Lambda again. How is that simpler than deploying a single Node.js application on DigitalOcean? The 2nd argument is scalability. I see how this is relevant, I'm wondering though how often it becomes really useful. How many products experience unpredictable spikes in traffic that cannot be handled by a single server costing $250/month? (that's one c5.2xlarge server on demand). I believe FaaS and Lambda are very useful, but I think I miss the point why would people move their whole applications there.

jxub 8y ago
There are frameworks like Serverless (the kinda default choice, `npm install -g serverless`), Zappa (in Python, not really up to date) and Apex (simple and nice option that is installed as a single Golang executable), that automate the back and forth between the API Gateway and Lambda in a config file.
matwood 8y ago
Have you done much with a framework like Serverless? The simplicity comes in because you can start writing business logic functions immediately. Plain Node typically uses a library like Express or Hapi. While not complicated, it is one more thing that is boiler plate and doesn't provide any business value. If the app needs a queue or messaging, sticking to plain node does not really change the need.
- simplify 8y ago
  Express and Hapi seem simpler than the Serverless framework you're replacing it with. You have to specify that one more thing[0] anyway, don't you? I honestly don't see how this is simpler. [0] https://github.com/pmuens/serverless-crud/blob/master/serverless.yml https://github.com/pmuens/serverless-crud/blob/master/server...

jxub 8y ago

There are frameworks like Serverless (the kinda default choice, `npm install -g serverless`), Zappa (in Python, not really up to date) and Apex (simple and nice option that is installed as a single Golang executable), that automate the back and forth between the API Gateway and Lambda in a config file.

matwood 8y ago

Have you done much with a framework like Serverless? The simplicity comes in because you can start writing business logic functions immediately. Plain Node typically uses a library like Express or Hapi. While not complicated, it is one more thing that is boiler plate and doesn't provide any business value. If the app needs a queue or messaging, sticking to plain node does not really change the need.

simplify 8y ago
Express and Hapi seem simpler than the Serverless framework you're replacing it with. You have to specify that one more thing[0] anyway, don't you? I honestly don't see how this is simpler. [0] https://github.com/pmuens/serverless-crud/blob/master/serverless.yml https://github.com/pmuens/serverless-crud/blob/master/server...