Echo VS Django Ninja

Echo mentions (0)

Django Ninja mentions (26)

• 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... - Source: Hacker News / 8 months ago

• Learning Django

  Personally, I also prefer django-ninja to DRF. Source: 10 months ago

• Django Views – The Right Way

  Or just use django-ninja if you are writing an API. Maybe it's just because I came from teams that used tornado and then fastapi but it seems like everything in this article would be solved by using a simpler interface for writing endpoints. https://django-ninja.rest-framework.com/. - Source: Hacker News / 11 months ago

• 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. Source: about 1 year ago

• Django 4.2 Released

  A good compromise I have found is to use Django Ninja [1]. It is inspired by FastAPI, so it has a lot of the nice things like the automatically generated Swagger/OpenAPI docs, as well as having routers as decorators, and using python types for automatic serialization. While I think FastAPI is great in its first class async support, Django has the Django ORM, plus Django Admin, which for me have been indisposable.... - Source: Hacker News / about 1 year ago