Zappa

I used to work for a startup that quickly grew to become one of the biggest Lambda users in my country (according to AWS). The entire business was serverless, not just Lambda but backend DynamoDB, APIGW, Cloudfront, etc. There was maybe 2 EC2 instances in the whole company. Having seen what that model of development can do from an operational/security/agility/scalability/efficiency perspective, I think the comments on HN about serverless saying "it's just CGI" or that they could do something similar without vendor lockin are honestly laughably ignorant. If you haven't messed with Zappa (https://github.com/Miserlou/Zappa) or Serverless Framework (https://www.serverless.com/) at least a little you are missing out.

That’s been around for ages. https://github.com/Miserlou/Zappa

Since most 'chatbot' stuff are callbacks, maybe Zappa might help you: https://github.com/Miserlou/Zappa You can host it yourself, or deploy it as a lambda/cloud function/etc.

I've found https://github.com/Miserlou/Zappa to be super useful for simple Lambda deployments. It's only for python, but I am pretty sure you have other solutions for node, ruby...

You can very easily deploy WSGI-compatible apps to AWS Lambda in seconds with the open-source library Zappa (https://github.com/Miserlou/Zappa). Zero server maintenance and zero cost if nobody is using your apps (I put up personal apps all the time with this paradigm, it's great). I love it so much I wrote a book about it: https://compellingpython.com/

Sort of related to this, but can someone explain to me why Zappa[1] isn't a bigger deal? It completely delivers, as far as I can tell, on the promise of deploying a WSGI app into a Lambda in a way that requires minimal configuration. And yet, the project seems to have stagnated somewhat. Maybe it just did everything it set out to do? I'm not sure, but when people say "forget about Lambda because you'll have to roll your own shit" I wonder if they've heard of Zappa or not. [1] https://github.com/Miserlou/Zappa

If you want fun and aren't afraid of some AWS, I highly recommend Zappa: https://github.com/Miserlou/zappa It's an amazing little piece of software, I am gobsmacked by how complete it is.

Inspired by Mapbox' rio-tiler [1], we wanted to build a modern tile server on the Python geo-stack that is optimized for AWS λ deployments (and that makes it beyond the proof-of-concept stage). The result is Terracotta, and I'm really happy with it, so I thought HN might appreciate it, too. Cold start times on AWS λ are as bad as expected, but once you got a sufficient number of instances running, it actually performs really well (mostly because loading a tile cover is so embarrassingly parallel). Besides that, Zappa [2] does a great job at taking the pain out of the AWS λ deployments and dependency management, so if you don't know that project yet I'd highly recommend you check it out. [1] https://github.com/mapbox/rio-tiler [2] https://github.com/Miserlou/Zappa

Sorry I'm too ashamed, I was learning basically all the technology involved. I can give a recipe: first 4 pages of this: * https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial... swapped out/skipped the sqllite3 for a single hardcoded user class (it's just me!) * throw in boto3 routes which do add/remove/clear ip rules, and start/stop instances, a list of checkboxable instances pulled from ec2 listing them * deploy using zappa https://github.com/Miserlou/Zappa some things that can trip you: * for the ip there's a stupid mistake I made, when testing locally you can request.get(myip) to get which ip to use, remotely you pull it off of request.remote_addr * your lambda will need a specialised IAM role to have rights to do all this, it's configurable in zappa config and I just clicked creating one through aws management console * this

If you are using serverless functions for something that a user sees, cold start time matters a lot more. Python's Zappa is made for taking Flask/WSGI apps to AWS lambda, and it actually has a configuration option to allow for automatic invocation of functions on a schedule to keep a pool of warm containers. https://github.com/Miserlou/Zappa#keeping-the-server-warm

Echoing the other comments, freelancing does make sense in your context. For the legwork of selling yourself and managing administrative stuff, there's https://gun.io as a freelance collective. I'm pretty sure there should be other parties offering that kind of arrangement, but I'm not aware of specifics. Note: I am not related to gun.io, just saw what they were offering through the CTO's Zappa docs and thought it was interesting. https://github.com/Miserlou/Zappa

Django running on Zappa (https://github.com/Miserlou/Zappa)

Hi HN, author here. Corral is my attempt at a performant, easy-to-deploy MapReduce. Unlike traditional frameworks like Hadoop, it uses AWS Lambda for execution and is “serverless” as a result. It was initially kicked-off by AWS adding Lambda support for Go, but draws on experience I’ve had using Lambda tools like Zappa[1] and Serverless[2] in the past. I think there’s a lot of interesting applications for using function-as-a-service platforms as executors in data processing frameworks such as this. If you’re interested more in the development/internals of this project, I wrote a blog post with more details: https://benjamincongdon.me/blog/2018/05/02/Introducing-Corra... [1]: https://github.com/Miserlou/Zappa [2]: https://serverless.com/