django-vitevue VS django-ninja

A modern alternative to DRF to build apis in Django is django-ninja. It is very simple to use and it takes advantage of the Pydantic schemas for validation and provides an auto-generated api doc. It is less complex than DRF. I recently made a template repo using this stack. It includes Django forms support in the Vuejs frontend. The Django config was made using django-vitevue that can help configuring a Vitejs frontend quickly.

The django-vitevue package helps configuring a Vitejs frontend for Django. It's main feature is a management command to configure a Vitejs app to compile to Django templates and static files. It handles single page apps as well as partial Django templates and works with existing frontends

Good point. I would add that sometimes having a modern spa dev env makes sense, to take advantage of major improvements in frontend stacks like Typescript or hot module reload servers like Vitejs, and use drf or graphql on the Django backend side. Btw I made a package to help configuring a Vitejs frontend to compile to Django templates, if anyone interested by this approach: django-vitevue

You could be interested by django-vitevue if you want to use Vitejs for your frontend. This packages helps generating a Vitejs configuration to compile your modern components based frontend app to a Django template and static files. It can compile to a partial template that can be included in your pages like any other template. Note: this package has just been rewritten and released, it is brain new

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 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.

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.

> 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...

Personally, I also prefer django-ninja to DRF.

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

Subscribe to this issue :D

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.