> 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 instal

> 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.