How we built scalable spatial indexing in CockroachDB
In this technical retrospective (2020), @orangechairs shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE ★ 153 points
TOTAL DISCUSSIONS 29 comments
I've used both approaches, GiST in PG and S2 in Mongo, and I feel that S2 has given me more tools to do queries like "which polygons contain this single point?" efficiently in my use case.
Blog post author here -- happy to answer any questions about the article.