Dealing with slow queries with multiple joins in data modeling

How can I get around slow queries with multiple joins? I have the following.
• First I join on module to get

slug.current

• Than on reference twice, to get

_type

and

territories[]._ref

• I could start keeping the module _id so I don't have to join to get the slug, but slugs are
nice 😐 • An experiment with expanding reference into array just blew up in my face with 3x query time
😝

I recommend modeling your data to avoid this sort of thing. Finding something by looking up whether it has a reference to something is "data model smell". In particular, slugs should be fast and within immediate reach, as a rule.

As a general rule, using

->

inside a filter like this is going to be slow. (We are actually working on an internal optimization that should make this much faster, but we don't know when we'll be able to release it.)

Ok, thanks 🙇‍♂️ I guess I'm damaged goods after decades modeling on an SQL stack. I'll have to look for another approach.