> e.g. you deploy your Django application to AWS Lambda and it automatically fires a lambda function when a view method is hit via a route. Is that a bad thing

> e.g. you deploy your Django application to AWS Lambda and it automatically fires a lambda function when a view method is hit via a route. Is that a bad thing in your opinion? Examples like that were very much a Day 1 use case, or at least intent, for a lot of AWS Lambda. When we were working on CloudFront Lambda@Edge it was explicitly the intent to move the compute out of the traditional data center or EC2 instance. We wanted to enable customers to run their entire application in this fully managed 'serverless' aspect where AWS can optimize along multiple axes on their behalf. Internally Amazon is a land of APIs, RPC, and federated services/business logic. Getting to the point where each API action, or internal method, would be hosted as a Lambda was entirely a goal. Source: Principal at AWS. Not in this space directly anymore, but spent time working on CloudFront & Lambda@Edge.