How exe.dev taught sqlc-generated code to invalidate its caches
davidcrawshaw · x · 2026-08-21
A post on the exe.dev blog by Ian Lance Taylor explains how they tackled distributed cache invalidation. Their proxies run worldwide and cache VM routing info (HTTP Host headers, SSH public keys, VM locations) rather than querying a central database on every connection—but VMs move and sharing states change, forcing them to solve the classic cache invalidation problem.
Their database layer uses the Go sqlc code generator, and they extended the sqlc-generated code to handle cache invalidation automatically. The post also covers why replicating the full database to every proxy was rejected: most data is irrelevant to proxies and some of it, like billing links, is sensitive.
More from coding & agent
- AgentRadio Research Enables Mid-Task Communication, Boosting Long-Horizon Task Resolution — import_jmr · 2026-08-21
- Open Source Tool Graft Gives Coding Agents Codebase Memory, Boosting Speed by 60% — alex_verem · 2026-08-21
- Graft: Persistent Codebase Memory Boosts Coding Agents' Speed & Efficiency — alex_verem · 2026-08-21
- Beyond pass/fail: devs debate how to evaluate agent decisions with real costs — KAIT2_1412 · 2026-08-21
- Polsia launches: 9 autonomous agents run full company operations — testingcatalog · 2026-08-21
- MCP Long-Running Tasks Demo: Showcasing Agent Persistence — dsp_ · 2026-08-21