The Art of Pivoting: How We Built Rainway
In this technical retrospective (2020), @youter 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 ★ 48 points
TOTAL DISCUSSIONS 7 comments
Although the technology is different, Gaikai were doing something extraordinarily similar to this back in 2011. The games ran on "an actual computer", and the entire i/o stream (video, audio, user input events) moved between that and a browser (on any platform).
Ultimately, Sony bought Gaikai and it vanished as standalone concept (rebranded as "Playstation Now", and mostly about zero day playing options).
For those of you who read the article and were still not sure what Rainway does:
Very cool product. Nowadays I don't play enough games to ever justify paying for something like that but I can totally see past me do it to play on my college notebook while in between classes :P
Would love to see their open source protocol in a cross platform screen sharing app! If the latency works for gaming, it certainly would work for simple desktop task.
This looks great, how is it free? Who buys my game data if that's the product?