How we built TryIon with BluetoothLE, Node.js, Websockets, and JSMpeg
In this technical retrospective (2014), @billylindeman 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 ★ 27 points
TOTAL DISCUSSIONS 4 comments
Thanks for the write up! Was very interesting to see of the use of jsmpeg.
As for why socket.io doesn't support binary, I'm guessing because it might be difficult to support that over some of the fallback transports. (That appears to be the reason in SockJS as well)
Who is your hosting provider? Did you see any ill-effects when you shared this with HN a few days ago?