Hetzner down in multiple locations
In this technical retrospective (2014), @babuskov 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 6 points
TOTAL DISCUSSIONS 1 comments
Very painful. Servers in multiple datacenters (inside hetzner) didn't help :/
I've been about 5 years with them now and never before something as serious as this have happened. There was single datacenter outage some time ago, but other than that it was unthinkable to me.
edit: http://www.hetzner-status.de/en.html ↗ Backbone connection fault