undefined | Better HN

0 pointsdanpalmer1y ago0 comments

My previous company had a sizeable Django monolith and did e-commerce stuff which is fairly latency sensitive. Used well, Django was perfectly capable of hitting 150ms per page which was fine for us. Some optimised pages were under 100ms.

Things we did: careful about N+1 queries, caching where obvious, API calls/emails/etc running in background queues.

Things we didn’t do: use a fast templating language (we used Django’s built in one and it was often our bottleneck), removing all database queries (we just had Postgres <2ms latency away), renormalising data (we were highly relational for most things).

Django is perfectly performant enough for almost all use cases, and insanely fast to develop with.

0 comments

rtpg1y ago

Yeah you can make Django go really fast, especially when you have pages that well scope what data they are pulling from (though you seem to know it better than me).

I think B2B SaaS, for "normal" teams (read: people not that adept at building scalable systems), when not careful, tend to make omnipages where about 20 different things are happening. Even just navigating to a page ends up triggering random side effects (driven by various needs).

There you can easily find yourself in a performance pit that you have to dig yourself out of (often redesigning features in the process to remove some stuff).

I just find that setting fairly easy performance goals can help to make perf seem more tractable.