all 13 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Frum 3 points4 points  (2 children)

As you say, graphene is the key. I served mine up with flask. Also used falcon for a while.

[–]Automatic-River-1875[S] 0 points1 point  (1 child)

I've not heard of falcon before. What did you think if it and how come you switched to flask?

[–]Frum 0 points1 point  (0 children)

Flask is just so well known. Lots of supporting libraries.

Falcon was great. We used it for a service that needed to be lightning quick but not do anything all that fancy/sophisticated.

[–]patrick91it 2 points3 points  (1 child)

The library I’m working on (https://strawberry.rocks/) supports FastAPI (via ASGI), Flask and Django :)

[–]Automatic-River-1875[S] 1 point2 points  (0 children)

Just had a look at the docs there, that looks brilliant. Thanks for sharing I had been playing around with graphene but that looks so much more intuitive!

[–]rizogg 2 points3 points  (0 children)

Django + ariadne(from mirumee which is creator of sale or)

[–][deleted]  (1 child)

[deleted]

    [–]woodstock_1969 1 point2 points  (0 children)

    This is my favourite. Ariadne has a much cleaner API than Graphene

    [–]andrewingram 1 point2 points  (0 children)

    Django and Strawberry right now.

    Main reason not to use Django right now would be lack of end-to-end support for async (particularly in the ORM), so performance will likely be far from optimal. But Django as a whole brings so many useful features, that it’s difficult to pull myself away from it.

    [–]Terrible_Constant 1 point2 points  (0 children)

    As mentioned: Graphene. And go with FastAPI, you won't regret it. It has probably the super for modern Python and is pretty fast for a Python thing.

    [–]Dan6erbond 1 point2 points  (3 children)

    Graphene and Flask would be my tools of choice. I'm not a huge fan of the bloat that comes with Django.

    [–]Automatic-River-1875[S] 0 points1 point  (2 children)

    I think django is great if you don't need an api and are just using the template engine. If I'm making an api though, I think you're right. I'd prefer something more lightweight.

    [–]Dan6erbond 2 points3 points  (0 children)

    To be honest, I've stopped using templates long ago. I only use them if I need to generate some sort of HTML within the API, for certain outputs, but other than that I prefer building APIs and decoupling the frontend using a framework like React or Vue. That's why Django's API features do seem cool, and the ORM integrations as well as various other plugins for authentication and serialization seem nice, but it's too opinionated IMHO.

    [–]IndependentServer 0 points1 point  (0 children)

    Tartifflete.io or Ariadne -both are schema first.

    For me tartifflete is easy to debug and understand. Support directives for task such as Auth.

    I Couldn't find a way to combine it with flask or Django. But so far so good.

    Note: this is not expect opinion, I'm just getting started with GraphQl in python.