How I built an app with 500,000 users in 5 days on a $100 server
In this technical retrospective (2018), @peter_d_sherman 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 Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE 28 points
TOTAL DISCUSSIONS 2 comments
Nice to read about building an MVP, but
A) the edit at the bottom of the article disproves his point. The competitor managed to get back online and increase to 2m users. Tech stack was irrelevant
B) 2.5 years later and there seems to be no trace of either app. Both were capitalising on the popularity of Pokemon Go and presumably neither were sustainable on their own. Again, tech stack is ultimately irrelevant.
(2016)
discussion at the time: https://news.ycombinator.com/item?id=12135484 ↗