Serverless: slower and more expensive

Re:Serverless: slower and more expensive by hdra on Monday September 23, 2019 @05:07AM (#21047172)

>The whole idea of serverless is so you don't have to manage infrastructure

Is this even achievable with Lambda though? Even with Lambda, you still have to configure your "infrastructure", just that instead of ELB and EC2, you now have to manage APIGW and Lambda, and any other "wiring" that you need to put in to do what you needed.

All in all, I can't really say Lambda is really all that "easy" considering options like AWS EB/ECS can be setup relatively easily.

[ Parent | on HN ]

Re:Serverless: slower and more expensive by pbalau on Monday September 23, 2019 @08:32AM (#21048272)

> you now have to manage APIGW and Lambda, and any other "wiring" that you need to put in to do what you needed.

You know those url.py files in a django install? Those are the equivalent of ELB/APIGW thing. You don't manage those, you make them once.

Not sure where you personally draw the line between app development and infra work, but for me "request that comes on this path, calls this function", either via ELB -> backend or APIGW -> lambda, or you know, whatever you use for your django app -> a function defined in a view.py, is app, not infra.

[ Parent | on HN ]

Re:Serverless: slower and more expensive by akhilcacharya on Monday September 23, 2019 @09:46AM (#21048870)

For the record, you can easily abstract that away or include it in your own code with frameworks like Chalice [0]

[0] https://github.com/aws/chalice

[ Parent | on HN ]

Re:Serverless: slower and more expensive by einaregilsson on Monday September 23, 2019 @05:16AM (#21047209)

There are definitely still things you need to think about with Lambda, like how much memory you want to allocate etc.

[ Parent | on HN ]