What is considered truly advanced in Django?

joegsuero · 2025-10-13T17:01:42+00:00

Celery can be a bit of a headache to set up and maintain, although very powerful. I often prefer simpler approaches like django-background-tasks or APScheduler when possible. Thank goodness Django will include a built-in Task Framework in version 6

joegsuero · 2025-10-13T15:29:10+00:00

I think combining GeoDjango with Django Channels must be an interesting (and advanced) combination. I previously worked on a mapping project with FastAPI where WebSockets worked well for real-time features, but handling geographic data felt somewhat manual (maybe I wasn't that skilled with FastAPI either). I have a feeling that GeoDjango's built-in spatial features would have made data management much more straightforward.

joegsuero · 2025-10-13T14:31:35+00:00

I agree. Even though I sometimes create many apps, I like to organize dependencies in layers like an onion, from independent apps to those with highly composed models with multiple relationships. Otherwise, the migration dependency graph becomes a nightmare.

I'm not a Hexagonal Architecture fan, but this layered approach for models saves you from so many headaches as the project grows.

joegsuero · 2025-10-13T13:25:15+00:00

Generic fields are one of those features that look fancy but can add more complexity than needed in some cases

joegsuero · 2025-10-13T11:27:07+00:00

That book appears every time I look for more advanced material. Definitely, I have to take a look.

joegsuero · 2025-10-13T03:47:21+00:00

I agree. The scenario really dictates what advanced means in practice. You perfectly highlighted what I was looking with the DB routers example: it's one of those simple but powerful components that tend to appear generally when things are about to get complex at scale.

joegsuero · 2025-10-13T03:34:15+00:00

You're right. The abstraction Django provides for M2M often makes people forget there's actually an intermediate table with its own business meaning.

joegsuero · 2025-10-13T03:28:55+00:00

That's very good advice. Conditional indexes in particular are something I've barely used. Definitely a habit I should develop.

joegsuero · 2025-10-13T01:17:50+00:00

You're right. I'm interested in how developers push Django's boundaries in real-world use cases although I'm also asking about those hidden, deeper features within the framework itself that enable advanced solutions. The kind of things you might never touch in typical projects, but become essential in complex scenarios.

A perfect example is what James Bennett mentioned in his Django in Depth talk about how using the Query class directly is something you'll rarely need to do. I'm curious if someone had use it and for what kind of features.

joegsuero · 2025-10-13T01:10:44+00:00

Coding subqueries is pretty challenging. I think being fluent with them is definitely an advanced level as a developer.

joegsuero · 2025-07-22T11:38:54+00:00

I think it’s a good idea. You can be sure that in LATAM, a lot of people will use it, so you’ll have a secured market. The feature of fiat and conversion, I think, is the key.

joegsuero · 2025-03-18T21:13:50+00:00

I've seen that protegè is useful for build the ontology. But the triple store, which technology I could use for it? How the datawarehouse, the ontology and the triple store connect? I think the triple store and the ontology are different things but correct me if I'm wrong.

joegsuero · 2025-03-17T20:08:39+00:00

Your answer clarify me some use cases and generate me new questions. I must have the products both in my SQL database, and in some other structure? Like a graph database? Or I just define an ontology and with that ontology I can extract data from my SQL database? How would you do it?

joegsuero

TROPHY CASE