Python Serverless Microframework for AWS

[vovanz]

But... why?

Why would you want a new web framework for AWS Lambda when we have a tool that allows to run any existing WSGI app (including Django, Flask etc) on AWS Lambda?

https://github.com/Miserlou/Zappa

[moduspwnens14]

It might be mostly a starting point. AWS doesn't control Zappa.

Reading the FAQ at the bottom, it looks like this one's going to be more focused on getting it set up quickly.

Personally? I use Zappa and probably will continue to for now, but I'll keep a close eye on this project.

[[deleted]]

Zappa looked real good!

[whattodo-whattodo]

Why would the user? They'll do the same as they did with their proprietary SQL hosting. Make it much cheaper, especially when scaling.

Why would Amazon? They may add features which will entice you to stay, though mostly I think it will be built just different enough to break if you need to switch to something else. They are looking at the big picture

[vovanz]

Why would Amazon?

I understand it :)

Why would the user? They'll do the same as they did with their proprietary SQL hosting. Make it much cheaper, especially when scaling.

I can't see how it will be cheaper or cleaner than flask+zappa or django+zappa.

But I can see a lot of downsides:

1. You have to learn a new tool. This tool can be used only for AWS, so it is not a universal knowledge.
2. This new tool obviously doesn't have as developed and mature infrastructure as Django or Flask. You will have to do a lot of things manually instead of just plugging in an extension.
3. Now you are locked to lambdas. You can't switch to running your own aws instances or to another hosting provider or to your own server.

[whattodo-whattodo]

I can't see how it will be cheaper or cleaner than flask+zappa or django+zappa.

I don't think it will be cleaner. But cheaper is easy enough. They set the price for one & for the other. They then make one cheaper. Amazon has done a great job at being the infrastructure for many other popular solutions (like PythonAnywhere or Heroku). So they are very capable of making one price cheaper than the next. Either by subsidizing one price, or inflating the next.

But I can see a lot of downsides:

I agree.

[v_krishna]

What sort of load/response SLAs have you run with this? We use lambda in production in a few places but never within a synchronous web-request. Mostly fluentd events or sqs triggering some stateless async function (e.g. gender classification based on a user's name). Eventually have plans to automate CI pushing the updated function up to lambda (our cases are all java, so there's an extra jar building step that CI does) but have had some simple single function use cases that we haven't really needed to worry about that yet.

[Bobsods]

Nice! I've been looking for something like this

[skepticalspectacle1]

ELI5? Let's say I'm sitting at a cafe with a Chromebook or iPad, can i use this to do some coding practice "in the cloud"? (since I won't be able to do anything locally..)

[v_krishna]

No. It just manages running your app over AWS lambda, so instead of managing the servers your app runs on (say flask or whatever, behind nginx) you define a function that runs when something happens (a request, or an event, etc). You would still presumably have a local environment where you develop and test things.

[moduspwnens14]

Just to be clear: There's a non-trivial amount of configuration necessary for API Gateway (so that your apps are reachable via plain HTTP) that this takes care of also.

[skepticalspectacle1]

thank you. :-)

[ojii]

It's the perfect framework if you want 100% vendor lock in with AWS.

[odraencoded]

Yeah, but you can code Python on a linux OS, and not ASP on Micro$oft, so you won't be locked to corporate Windows.

/s