graphene-django VS Zappa

Graphene-Django Graphene-Django is a powerful library that integrates the GraphQL query language with Django, allowing for the development of flexible and efficient APIs. It seamlessly combines the expressive power of GraphQL with the simplicity and elegance of Django, enabling us to design APIs that fetch only the data the clients need.

Install Graphene and Graphene-Django. Graphene is a tool that makes working with GraphQL in Python easy, while Graphene-Django adds some additional abstractions to make adding GraphQL functionality to your Django project a breeze. To install Graphene and Graphene-Django, run the following on your command line/terminal, pip install graphene graphene-django.

But if you must take a look graphene for graphql. https://docs.graphene-python.org/projects/django/en/latest/

You will find a lot of videos about Django on YouTube. If you need a REST API try DRF. If you want GraphQL try Graphene Django. For WebSockets there is Channels. If you don't want to bother with having an API for your frontend but you still want that SPA feeling try HTMX.

I've used Graphene + Graphene Django to write GraphQL APIs for several years now, but graphene-django unfortunately seems to (mostly) be abandoned now.

In conclusion, the Graphene-Django library makes it easy to get started with GraphQL integration by allowing you to use your existing Django models as the data source for your GraphQL API and automatically generate the schema. For more information, check out the documentation.

Django ninja strawberry Graphene

in my last project I used graphene to build a Django backend application with GraphQL. It seemed like the best framework to adopt graphql in python at that time in terms of stability and maturity.

If people aren't familiar, there's a similar project for Python that's fantastic: https://github.com/zappa/Zappa

Chalice was a consequence, a reaction from AWS to the release of (Zappa Framework)[https://github.com/zappa/Zappa] that provide a very good alternative to migrate very quickly a Django/Flask or any WSGI compliant solution in Python.

Use Zappa https://github.com/zappa/Zappa and host as a Lambda, simple setup and deployment, Lambda only costs when processing requests, no servers to mess around with

One of my favorite options that is probably the most cost-effective is to deploy using a 'severless' model on AWS Lambda using zappa which supports deploying Python webapps to AWS in this way. Zappa also makes it super easy to deploy in just a couple commands! The README includes instructions for everything you might need, including handling sensitive information like your database passwords, running django management commands, setting up DNS, etc.

Deployment works nicely with Docker. I often use AWS AppRunner because it's really easy and just scales. Some people use AWS Lambda with Zappa but I don't recommend it unless you really want to spend less than $15 a month. You will probably need Django Storages to save uploads to an S3 bucket. At some stage you might want to put a CloudFront distribution in front of everything but the configuration of the caching behaviour might be a bit confusing when you do it the first time.

It doesn't have to be an either-or! I have several apps in production that were developed on Django or Flask, and deployed to Lambda using Zappa.

If you need a relational DB, you can use AWS Aurora or RDS and use cloud functions ('lambda' in AWS) that you can invoke with HTTP to process the document first. Zappa will do a lot of the configuration for you if you go that route.

Lambda + API gateway, this library bundles a Django application into a lambda https://github.com/zappa/Zappa . 1 million free invokes from aws, scale to zero, plugs into your RDS

I use Zappa, it just schedules a frequent execution of the lambda: https://github.com/zappa/Zappa#keeping-the-server-warm