[Thread] Former exec describes Amazon's transition from Sun to HP/Linux servers in early 2000s, that risked bankrupting the company and laid foundations for AWS
Dan Rose / @danrose999 : Tweets: @raifshareef_ , @corry_wang , @det_conan_kudo , @jan_eeckhout , and @ericdungan Tweets: Raif Shareef / @raifshareef_ : “The best companies look at every challenge as an opportunity and engrave that mindset into their culture.” Interesting read. Culture eats strategy for breakfast. Whatever decisions and policies made here in Maldives are shortsighted. https://twitter.com/... Corry Wang / @corry_wang : 1/ Thoughts on the Myth of the “First Mover” This thread by @danrose stirred something I've been thinking about for a while - the myth of first mover advantage To this day, most people assume Amazon Web Services was the first cloud computing service. This isn't quite true https://twitter.com/... Neal Gompa / @det_conan_kudo : Cool thread on the rise of Linux at Amazon/AWS! https://twitter.com/... Jan Eeckhout / @jan_eeckhout : Interesting story how the growth of Tech was all about early investment and economies of scale https://twitter.com/... @ericdungan : @QuinnyPig @awscloud For the geekier, post on how Amazon moved to Linux operating system. Includes info that AWS came about due to over capacity required during Nov-Dec holiday busy period https://twitter.com/...
Context & Ripple Effects
Dan Rose's thread retells a decision point that predates AWS as a product: Amazon's early-2000s migration off Sun servers onto HP hardware and Linux, which a former exec says came close to bankrupting the company. The payoff was architectural — standardized, internally shared infrastructure that later became sellable capacity.
That origin story connects directly to how AWS runs today: Amazon exposing internal operations to external competition to kill inefficiency, and small independent teams building on common internal systems that scale. The same common substrate that once saved Amazon is now the lock-in an anonymous AWS engineer describes as easy to enter and hard to leave.
First-order effects
- Amazon bet its survival on abandoning Sun's proprietary servers for commodity HP/Linux hardware — if the migration had failed mid-flight, the company lacked the cash cushion to absorb it.
- Sun lost a marquee customer at exactly the moment its high-margin Unix server economics were being replaced by cheaper Linux boxes.
Second-order effects
- The standardized internal platform Amazon built to cut costs became AWS itself, turning a defensive IT project into a business that now competes with the very hardware vendors it once bought from.
- HP and other commodity vendors gained the enterprise workloads Sun shed, while every rival retailer faced the same choice: replicate the platform investment or rent it from Amazon.
Third-order effects
- The pattern — a cost-driven internal migration hardening into a dominant external platform — set the template for cloud concentration, which is why debates like repatriating workloads to cut cloud spend are now framed against AWS gravity rather than any single vendor contract.
The trend: Infrastructure built for survival inside one company keeps converting into market-defining platforms, and the industry is only now testing whether that gravity can be reversed.