Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 5.2 Released

djangoproject.com

Post reply on HN
Print view View original

11–20 of 25 posts

Re: Django 5.2 Released

#11

Post by mrj »

belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

You don't have to choose between them, django-ninja gives you the same routing experience but without losing all the batteries included experience of Django.

Re: Django 5.2 Released

#12

Post by jdahlin »

belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

I personally choose Django as often as I can, the tooling is considerably better and the ecosystem is significantly larger. Admin is a killer app until you know exactly what you're developing. It's trivial to setup tests with pytest-django, use with a mypy via django-stubs, with django-ninja you can fastapi like routes and models based on pydantic, etc etc etc.

Re: Django 5.2 Released

#13

Post by rglullis »

belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

It's basically impossible to beat Django's breadth of packages. If you are working with a traditional app, the admin alone can give you 90% of the functionality you'll need.

Re: Django 5.2 Released

#14

Post by newswangerd »

belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

I've been developing in Django with Django Rest Framework for 10+ years and just recently built my first FastAPI project, so I may be a little bit biased here.

Django takes care of a lot of common functionality for you. The biggest things for me are:

- Authentication: this includes safely handling sessions, cookies, password hashes as well as integrations with SSO providers via libraries like Social Django.

- ORM: love it or hate it, the ORM just does everything. You mostly don't need to worry or think about migrations or database support.

- Admin panel: the builtin admin panel is a great way to get a quick UI that can, in some cases, handle a pretty big swath of the UI needs for your app.

With that said, there are some things that I LOVED about FastAPI. Using pydantic for serialization is way nicer than the serializers you get from Django Rest Framework. The DRF serializers just feel slow and antiquated after using pydantic. FastAPI is also much lighter weight, and works great if you just need a quick and dirty API server.

I think that my recommendation would be to use FastAPI for microservices and Django for anything that needs to handle more than a few REST API endpoints. All the extra functionality in Django is great if you want to build a production monolith, but all those extra features are unnecessary bloat for microservices.

Re: Django 5.2 Released

#15

Post by pphysch »

999900000999 wrote: post #6

I just started using Django a few weeks ago, but it's so much more flexible than Supabase/Firebase. I feel like I have much better control now.

I think the flexibility and agility in domain modeling is the magic sauce of ORMs like Django. The Model definition directly drives migrations and form generation (incl Admin GUI).

If you know exactly the product you are making and don't need to iterate much on the domain model, frontend-oriented frameworks like Supabase and FastAPI make sense.

Re: Django 5.2 Released

#16

Post by hedgehog »

belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

Different purposes. If you're building a user-facing web app Django, if you're building an API-only service then FastAPI. To me the big selling point of Django is it's a batteries-included way to build a web app that works with a bunch of pre-integrated stuff including the ORM, form validation, admin site, background tasks, etc, and it is used by so many people that you are unlikely to run into any sharp edges.

Re: Django 5.2 Released

#17

Post by graemep »

newswangerd wrote: post #14
belter wrote: post #4

In 2025, how much does it still make sense to go the Django way vs FastAPI ? Looking for well founded opinions. Not controversy.

I've been developing in Django with Django Rest Framework for 10+ years and just recently built my first FastAPI project, so I may be a little bit biased here. Django takes care of a lot of common functionality for you. The biggest things for me are: - Authentication: this includes safely handling sessions, cookies, password hashes as well as integrations with SSO providers via libraries like Social Django. - ORM: lo…

I agree, about the admin in particular because its something a lot of frameworks do not have.

I have used DRF in the past but I am a bit worried about it future. Discussion here: https://news.ycombinator.com/item?id=43510495

Django Ninja looks promising.

Re: Django 5.2 Released

#18

Post by 999900000999 »

pphysch wrote: post #15
999900000999 wrote: post #6

I just started using Django a few weeks ago, but it's so much more flexible than Supabase/Firebase. I feel like I have much better control now.

I think the flexibility and agility in domain modeling is the magic sauce of ORMs like Django. The Model definition directly drives migrations and form generation (incl Admin GUI). If you know exactly the product you are making and don't need to iterate much on the domain model, frontend-oriented frameworks like Supabase and FastAPI make sense.

Supabase was neat to get started with. The moment you need any complex backend logic it all falls apart.

A lot of things, like CRUD editing in admin, is just done for you in Django.

My other issue with Supabase is just how difficult hosting actually is. Requires a whole lot of magic/weird undocumented trickery. Vs Django which just works.

It probably really depends on what you need to build though.

Post reply on HN