Bare Metal Solution: Enabling Specialized Workloads in Google Cloud
In this technical retrospective (2019), @bretpiatt 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 ★ 22 points
TOTAL DISCUSSIONS 6 comments
This is essentially just a co-located box, that you connect to your virtual network over a VPN/interconnect. Why is it not inside the virtual network? Why is the pricing hidden behind a sales person? That seems like the first cloud instance to have hidden pricing...
They don't call it out in the announcement, but this was published in the same week as the "Supercomputing" conference - GCP hasn't had an answer for HPC workloads thus far, so maybe this is their attempt.
I wonder if it's competitive with Rackspace and similar, or if they are charging a premium and/or things like egress.