django-ninja
connexion
Our great sponsors
django-ninja | connexion | |
---|---|---|
70 | 23 | |
6,197 | 4,416 | |
- | 0.5% | |
9.1 | 8.2 | |
4 days ago | 10 days ago | |
Python | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-ninja
-
Ask HN: What Underrated Open Source Project Deserves More Recognition?
Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.
[1]: https://django-ninja.dev/
- Django Ninja is a web framework for building APIs with Django
-
UtilMeta Python Framework VS django-ninja - a user suggested alternative
2 projects | 3 Feb 2024
Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.
- Django Ninja
-
Ask HN: What Python libraries do you wish more people knew about?
I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.
It's gaining popularity but is still widely unknown.
-
Building a Blog in Django
> The only place I really see Django at large companies is as an api using DRF or something.
This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].
Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.
There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.
[1] https://django-ninja.rest-framework.com/
[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...
-
Learning Django
Personally, I also prefer django-ninja to DRF.
-
Why I chose django-ninja instead of django-rest-framework to build my project
Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth
-
Built This GPT-Powered Document Search and Question Answering App with Django
Subscribe to this issue :D
-
Django 4.2 released
Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.
connexion
-
Write OpenAPI with TypeSpec
I like the idea, especially the TS-like syntax around enums and union types. I've always preferred the SDL for GraphQL vs writing OpenAPI for similar reasons.
I echo the sentiment others have brought up, which is the trade-offs of a code-driven schema vs schema-driven code.
At work we use Pydantic and FastAPI to generate the OpenAPI contract, but there's some cruft and care needed around exposing those underlying Pydantic models through the API documentation. It's been easy to create schemas that have compatibility problems when run through other code generators. I know there are projects such as connexction[1] which attempt to inverse this, but I don't have much experience with it. In the GraphQL space it seems that code-first approaches are becoming more favored, though there's a different level of complexity needed to create a "typesafe" GraphQL server (eg. model mismatches between root query resolvers and field resolvers).
[1] https://github.com/spec-first/connexion
-
Connexion 3 released!
Connexion is a popular Python web framework (~ 5 million downloads per month) that makes spec-first and api-first development easy. You describe your API in an OpenAPI (or swagger) specification with as much detail as you want and Connexion will guarantee that it works as you specified.
- Connexion 3.0 Released
-
Show HN: REST Alternative to GraphQL and tRPC
> While REST APIs don't generally provide the same level of control to clients as GraphQL, many times this could be seen as a benefit especially in scenarios where strict control over data access and operations is crucial.
Rest is more secure, cacheable, and more performant on the server side as field resolution doesn't need to happen like it does with GraphQL. It is not more performant on the client side, and this is a trade-off, but I favor rest applications over GraphQL ones as a DevOps engineer. They are much easier to administer infrastructure-wise, I can cache the requests, etc.
Data at our company suggests that several small queries actually do better performance-wise than one large one. We switched to GraphQL a year and a half ago or so, but this piece of data seems to suggest that we might have been better off just sticking with REST. My suggestion to that effect was not met with optimism either on the client or server side. Apparently there are server-side benefits as well, allowing for more modular development or something like that.
I have used OpenAPI using connexion[1]. It was hard to understand at first, but I really liked that the single source of truth was one schema. It also made it really easy to develop against the API because it came with a UI that showed the documentation for all the rest end points and even had test buttons.
1: https://connexion.readthedocs.io/en/latest/
-
Ask HN: Why is there no specification for Command Line Interfaces?
What's the use case? I was thinking about this exact issue because my product ships several CLI tools, but I wasn't convinced it would be worth the effort.
An OpenAPI specification describes an HTTP interface, and I see it as useful because it makes it easier to write code in language-of-choice to generate HTTP requests (by generating client libraries from the OpenAPI spec).
For a CLI, the interface is the command-line. Usually people type these commands, or they end up in bash scripts, or sometimes they get called from programming language of choice by shelling out to the CLI. So I could see a use case for a CLI spec, which would make it easier to generate client libraries (which would shell out to the CLI)... but it seems a little niche.
Or maybe, as input to a documentation tool (like Swagger docs). I would imagine if you're using a CLI library like Python's Click, most of that data is already there. Click Parameters documentation: https://click.palletsprojects.com/en/8.1.x/parameters/
Or maybe, you could start from the spec and then generate code which enforces it. So any changes pass through the spec, which would make it easy to write code (server and client-side) / documentation / changelogs. Some projects like this: Guardrail (Scala) https://github.com/guardrail-dev/guardrail , and Connexion (Python) https://github.com/spec-first/connexion .
But without this ecosystem of tooling, documenting your CLI in a specification didn't really seem worth the effort. Of course, that's a bootstrapping problem.
-
Flask is Great!
Connexion is a framework on top of Flask that automagically handles HTTP requests defined using OpenAPI/Swagger.
-
What is the best practice for mapping JSON requests to objects and back to JSON?
I recommend you create a OpenAPI Specification and implement a python module that you expose via connexion or on the cli via click(for easy testing).
-
Flask-Powered APIs: Fast, Reliable, and Used by the World's Top Companies
I'm here because Swagger-CodeGen created flask-Connexion boilerplate for python.
- Python REST APIs With Flask, Connexion, and SQLAlchemy – Part 1 – Real Python
-
Does anybody know any good resources I could use to study ISP architecture?
Personally we just prov them using librouteros and flask-connexion/openapi.
What are some alternatives?
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
flask-restful - Simple framework for creating REST APIs
django-rest-framework - Web APIs for Django. 🎸
Flask RestPlus - Fully featured framework for fast, easy and documented API development with Flask
fastapi-admin - A fast admin dashboard based on FastAPI and TortoiseORM with tabler ui, inspired by Django admin
flasgger - Easy OpenAPI specs and Swagger UI for your Flask API
drf-spectacular - Sane and flexible OpenAPI 3 schema generation for Django REST framework.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
eve - REST API framework designed for human beings
cookiecutter-django - Cookiecutter Django is a framework for jumpstarting production-ready Django projects quickly.
falcon - The no-magic web data plane API and microservices framework for Python developers, with a focus on reliability, correctness, and performance at scale.