Hacker News new | past | comments | ask | show | jobs | submit login

For people who run their apps like this, do you find the complexity is greater or lesser than running e.g. Express + nginx in richer containers?

This looks very cool, but seems ripe for some ugly emergent behavior to appear.

After the initial “cost” of figuring out how to configure the services, I’m finding the complexity far less than containers.

Many concerns are removed from my application code and build and deploy systems by Lambda and API gateway.

You just throw some zip files in S3 and you have a web service.

No more image registry, container orchestration, load balancers, AMIs, autoscaling, etc.

You also get to remove things code around CORS, auth, polling etc. from your app.

I have a bunch of writing on how FaaS makes things easier here:


Like all things, it depends. Your application architecture complexity is going to go way up, but your devops / sysadmin complexity goes to zero.

I run a web hosting service, and while my application code is a bit more complicated now, I don't have to worry about monitoring ec2 instances, process managers, and that's worth it. That particular trade of is worth it.

If you manage an application with a high level of application logic, such that keeping servers alive is relatively simple, maybe the calculus works out differently.

Node apps are incredibly easy to deploy to Elastic Beanstalk. For most users, the pros of Lambda are probably outweighed by the cons (even though the concept is fantastic).

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