How we built the new gocardless.com
In this technical retrospective (2015), @jackfranklin 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 10 points
TOTAL DISCUSSIONS 4 comments
I turned off JavaScript to see if the site still worked: it did. I then navigated to different pages to see if it was slower than the "blindingly fast" the blog post promises: I couldn't detect any difference.
In summary, I have no idea why you would use React to build a static site, but I sure hope they had fun doing it.
I love what you guys have done. I'm interested to know what is the rationale for this? Are you finding that it helps improve conversion or something? Basically help me convince the business side of my company so that I can use this for our site too. :)