Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



I've tried to use Zappa for a non-trivial personal project to run a Django app and I found:

- Super nice, low config API

- easy to deploy

- great out-of-the-box support for async tasks (no Celery! woo!)

but:

- It was a nightmare getting certain Python libraries (eg. Pillow, psycopg) to work in the AWS Lambda environment

- It really sucked having to deploy to AWS in order to debug issues which cannot be reproduced locally (eg. library)

- It seems hard to get away from using AWS tools to observe your code in prod (eg. CloudWatch for logs)

- I still needed a database to maintain state, DynamoDB didn't work with Django's ORM and was surprisingly expensive, and if I'm going to shell out $10/mo for a Postgres RDS instance then I may as well run the whole thing on EC2 anyway

I think Zappa is a really nice tool for some niche use cases, and I'd definitely turn to it if I needed to stand up some small, stateless serverless service, but I would hate to support and debug it as a web app in prod.

project: https://memories.ninja

zappa version: https://github.com/MattSegal/family-photos/tree/lambda-hosti...

ec2 version: https://github.com/MattSegal/family-photos


YES.

Zappa got me out of a massive hole several times. I'm not a webdev, and we arn't a web company, so we don't have a web deployment pipeline.

Having Zappa makes our life very simple and cheap. The best part is that local and "prod" are equally easy to spin up.

The simple integration to DNS, SSL, api gateway, is a wonder.

The only downside is the permissions management is a massive pain, and assumes that you have admin permissions.


I tried to use Zappa and my experience was that it didn't support tires of callbacks I needed it to. After I patched it up to do what I want I realized that handling calls directly was actually simpler than using Zappa and Zappa made my application huge.

I understand that primary use of Zappa is a web application, but I have reservation about that as well. The "serverless" applications aren't really server less, they just have VMs spun on demand and it's only good idea when you have a service that most of the time is idle.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: