Django-Styleguide VS django-ninja

There are alternatives, such as HackSoft's Django style guide, but fat models, thin views is usually good enough.

I think this is a great resource. The only comment I have is on the Thin Views chapter. Instead of attaching logic to the models, I like to make a services.py file in my app that has functions that satisfy all sorts of business logic.

Here's another opinionated Django guide: https://github.com/HackSoftware/Django-Styleguide if anyone's interested

you can follow the Django Style Guide by Hacksoft. They have awesome style guide for you on github https://github.com/HackSoftware/Django-Styleguide

I would also recommend taking a look at HackSoftware's django styleguide repo. I found applicable. You don't have to follow it religiously (or at all) but still brings up some good food for thought.

I've read from Django Styleguide, Two Scoops of Django, Django for Startups, Still No Service, and a few threads even here in this subreddit (they largely reference above).

Perhaps the Django style guide is suitable? It definitely isn't a basic tutorial but perhaps it's too advanced? https://github.com/HackSoftware/Django-Styleguide

well Django encourages you to tightly couple your django code with your views but even I do not like that way of doing it. So what I had started following HackSoft's Django styleguide - https://github.com/HackSoftware/Django-Styleguide to write my Django code.

Django-Styleguide – Django styleguide used in HackSoft projects

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.