korrents

korrents · piece

Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go

Brandur Leach · 28 May 2024

Read the piece on brandur.org ↗

2 korrents from this piece ↓

Brandur Leach did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

  1. Our reading

    N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.

    Their wordsThis practically invisible problem is probably number two to only forgotten indexes as the most common reason for poor performance of web apps around.

  2. Our reading

    Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity.

    Their wordsDespite Go's ad nauseum verbosity, it's no less susceptible to N+1s than a language heavy in metaprogramming like Ruby.

Keep reading