4 ms·

I agree that we will see all of those, except the last one. It's no surprise that we're bending around, that's normal. But when we get back to the "feature pari

I agree that we will see all of those, except the last one. It's no surprise that we're bending around, that's normal. But when we get back to the "feature parity with the past" things will still look very different. We're talking about fully managed systems here that you can compose together to get parity with what you have today with unmanaged systems. I also don't think the time limit on lambdas will extend much further than it is today. Not sure on that one.

Thorentis 6y ago
I'm imagining the full circle looking like web frameworks "compiling" their controller methods down into lambda functions. 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. This is already happening where people are deploying static sites backed by lambda function APIs.
- donavanm 6y ago
  > 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.
- mwarkentin 6y ago
  That’s been around for ages. https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa

Thorentis 6y ago

I'm imagining the full circle looking like web frameworks "compiling" their controller methods down into lambda functions. 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. This is already happening where people are deploying static sites backed by lambda function APIs.

donavanm 6y ago
> 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.
mwarkentin 6y ago
That’s been around for ages. https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa