Marlon and Andreas — two Vespa engineers who have variously broken, debugged, and apologised for Vespa in production — will walk you through what happens when:
-
A search company's public search demo gets garbage-collected by S3 because the demo was so stable nothing had changed in 180 days,
-
A customer asks Vespa for ten specific document IDs and reliably gets four back (eight engineers, nine hours, the fix is one query parameter),
-
A single grouping query with an empty array crashes every search node simultaneously, and
-
A customer feeds 25 KB of text containing 11,167 Unicode replacement characters — text so broken our indexer correctly decided it must be binary.
Each story is short, technical, and at our own expense. The through-line: distributed systems where some invariants are local-only, "defensive" code that turned out not to be, optimisations that quietly hide your blast radius — and a healthy reminder that even the people who write search can't always find their own documentation.
Andreas Eriksen, Vespa.ai & Marlon Saglia, Vespa.ai
