Zappa

While wasting a Friday evening with an indecisive group, I discovered that there wasn't a good polling site that used run-off voting and worked well on mobile, so I made FreePoll. It's good for simple things like deciding what food to eat: https://www.freepoll.online/p/NBEBCAHNU But also for more important things, like deciding what features to work on next for your software project: https://github.com/Miserlou/Zappa/issues/536 Would love any feedback you guys have to offer!

Was really expecting a lot more out of the announcements today as well. Python3, GPUs, custom containers, larger packages.. the list goes on.. That being said, re: Python 3, you should keep a close eye on Zappa (https://github.com/Miserlou/Zappa) - as we've got a surprise in store that may delight you!

Zappa actually uses some of Kappa under the hood, but with many many more features. Learn more here: https://github.com/Miserlou/Zappa

I'm biased saying this, but Chalice is a half-baked rip-off of Zappa[0], deliberately nerfed by Amazon to lock you into the AWS stack. If you want to see an example of how easy it is to use Zappa + Lambda + DyanamoDB, you can check out Zappa BitTorrent Tracker, which can use S3 or DynamoDB as a back-end.[1] As a bonus, Zappa has had both local and remote environment variables as a feature for months - although it's pretty cool that this new announcement can use KMS, although that will of course mean more vendor-lock in if you choose to go that route. [0] https://github.com/Miserlou/Zappa [1] https://github.com/Miserlou/zappa-bittorrent-tracker

I've recently deployed a small Flask based micro-service for an internal tool leveraging Zappa[0] to deploy it to Lambda/API Gateway. Overall it's been a really smooth experience. I'm looking forward to using it again. [0] https://github.com/Miserlou/Zappa

If you're a Python user, there is absolutely no reason to user Heroku over Zappa[0]. Zappa is cheaper (usually free), it's faster, it has auto-renewing Let's Encrypt certs out of the box, it doesn't have a warm-up time, it's more scalable and you never have to worry about ops. Heroku's day has come and gone, quite frankly. Obviously, I'm biased because I'm the author, but you should evaluate it for yourself. [0] https://github.com/Miserlou/Zappa

Author of Zappa[0] here - glad to see more F/OSS implementations in this space - see also OpenWhisk and I think there was another (IronIO? MetalIO? Something like that?) - but I think an important piece that's missing is a F/OSS implementation of API Gateway! That's part of the reason the AWS is still the leader of the pack IMO. [0] https://github.com/Miserlou/Zappa

There is an excellent Django package/adaptation for Lambda or serverless mode [1] [1] - https://github.com/Miserlou/Zappa

It depends on what framework if any you choose to serve websites with. If you something like Chalice or Serverless then yes you are stuck with Lambda. But you use something like Zappa (https://github.com/miserlou/Zappa) that is basically converts API Gateway's request object to one that is WSGI compatible then you can take your app and skip down the road if you get ticked off with Lambda. The Heroku comparison one isn't a fair one either. The waya you pay for Heroku dynos is very similar how you pay for EC2 or any other VM. You are billed by the microsecond that part is very important and while technically you have a 100 req/s limit to start with it is a soft limit if you ask to have it removed. It is probably more useful to compare it to Google App Engine but even that isn't fair.

I got burned by Parse on this already. One of the nice things about Zappa (https://github.com/Miserlou/Zappa) is that you can return to a non-serverless architecture if you want to.

https://github.com/Miserlou/Zappa might be more useful to you.

Why not https://github.com/Miserlou/Zappa?

I have started the lambda-packages[1] project for use with Zappa[2] and other Python on Lambda projects. [1] https://github.com/Miserlou/lambda-packages [2] https://github.com/Miserlou/Zappa

Most of the issues described in the article are solved by projects like [0], [1] and [2]. [2] was particularly easy to work with (tried it with a standard installation of Django CMS and it was working very well, only in US regions) and the advantage is that you can still work locally as you would usually do, even keep a testing environment for CI on a managed server, and just replace the production server with it. [0] https://github.com/serverless/serverless [1] https://github.com/Miserlou/Zappa [2] https://github.com/Miserlou/django-zappa

This reminds me of Zappa [0], only Zappa actually runs on AWS Lambdas. Although they readily admit it takes a lot of hacks to get WSGI working within a Lambda function. 0: https://github.com/Miserlou/Zappa