How we built our Real-time Analytics Platform
In this technical retrospective (2014), @jdorfman 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 17 points
TOTAL DISCUSSIONS 11 comments
TL;DR: TokuMX (MongoDB upgrade) through Redis with Go on the back end and Node.js for the API.
The biggest take-away for me was that someone is selling ($2500/server/year for hot backup + support) an improved ('accelerated speed for inserting data as well as compression') GPL2 MongoDB.
Awesome job. Curious did you investigate fluentd (http://www.fluentd.org ↗)?
Also, seems a bit odd to use MongoDB for write optimized work loads, since it essentially has a global write lock. Doesn't Cassandra perform better at writes?
I stopped using MaxCDN since a website I took offline months earlier suddenly achieved "bandwidth overage" according to them, and my credit card was charged.
Recently, they advertised they now provide server logs to prove usage, but I'm done with them.