Virtual Bare Metal: DevStack Multi Node on EC2
In this technical retrospective (2014), @geertj 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 13 points
TOTAL DISCUSSIONS 11 comments
I may be mistaken, but aren't the larger EC2 machines priced fairly linearly with the improved resources? i.e. a machine with 2x the resources typically costs 2x as much?
If this is the case then can someone let me know the use case? Is this for better manageability? Or is it to overcommit (i.e. run 3x 4gb ram nodes on 8gb of ram).
Other then that I can't see the advantage over dynamically spinning up & down nodes as required directly on AWS.
So can I run linux instances on this DevStack cluster that I can run VM's on so I can host docker containers. I feel that two levels of virtualization is not enough for me and would like three or four.
Hey, I'm working with the Ravello team. Happy to answer any questions.