26 ms·
When Amazon Switched from Sun to Linux
- billwashere 6y agoLink to consolidated version https://threadreaderapp.com/thread/1347677573900242944.html https://threadreaderapp.com/thread/1347677573900242944.html
- Mountain_Skies 6y agoWhy has it become so popular to break what should be blog posts into endless streams of tweets? The content is unreadable.
- forgotmypw17 6y agoi just skip it, along with js-only sites. i used to get frustrated like you. then i realized that both correlate heavily with crap content, which makes sense, since the same person writing is also choosing the platform. these days i say thanks for their self-filtering and move on to the next link. there is more content than i can read as it is.
- mark-r 6y agoThis is why I like Hacker News. If the content transcends the medium, it will get a high enough ranking to bubble to the front page.
- stevewodil 6y agoProbably audience reach, I'm guessing tweeting the information directly as opposed to a link to a blog results in more engagement. As for why Twitter specifically it's because that's where their followers are, it will get the most views presumably vs. other platforms or mediums. FWIW I personally enjoy tweetstorms, I'm not sure why. I think the break in between each tweet is nice, it's like reading a series of messages rather than a blog post and I find myself more engaged. It also means the author has to be fairly concise
- saurik 6y agoThis is largely why I do it. I have half a million twitter followers, and while I can write it on my blog and then tweet a link, it is nowhere near as effective as just publishing the content directly on Twitter. FWIW, I used to despise it when people did this (post massive threads of messages), but frankly I think they fixed the UI for this years ago, and just don't understand the complaints anymore: you click the link, and can scroll through messages as if it were an article. Between it auto-flowing the messages and the longer tweet length of 280 characters, I honestly don't see any advantage to those "thread readers" people keep linking to... they don't even have larger information density, which is ridiculous. (Hell... they frankly seem to make the text harder to read!) (And yeah: I carefully write my tons of text on Twitter such that every single message is a carefully enough crafted thought that they could just about stand alone, which I think is actually good for the content.)
- stevewodil 6y agoWow, it is SO weird to see the name "saurik" replying to my comment. I remember in middle school jailbreaking my iPod touch to install all kinds of cool tweaks from Cydia, and I'm sure that exposure led me to continue messing around with electronics. Thank you for all you did for the community, I attribute a lot of my interest in computers and coding to the early jailbreak days.
- enw 6y agoHey, sorry for being off-topic. Just wanted to say thanks for making Cydia! It feels very nostalgic to me.
- tjoff 6y agoyou click the link, and can scroll through messages as if it were an article. No you can not. Often times the posts are not in order. You have to expand multiple times and if you are unlucky you get pulled into another direction and miss half the story. Unreadable isn't hyperbole. Maybe you have to have an account for it to be usable? Note: the posted twitter-thread is the first I've seen that actually works for me. Not sure why that is.
- 6y ago
- justinv 6y agohttps://threadreaderapp.com/thread/1347677573900242944.html https://threadreaderapp.com/thread/1347677573900242944.html
- hyakosm 6y agoYou can comment or share individual blocks in one click, I guess it's the point of that.
- lscotte 6y agoI don't know but agree it's unreadable and terrible, so I don't bother to read them.
- pengaru 6y agoconvenience and laziness are powerful forces
- markmark 6y agoBecause most people don't have blogs these days and it's not worth setting one up for a one-off short thing like this. It's also perfectly readable for its target audience of people who use twitter.
- sumnole 6y agoagreed, but still better than reading a book for what could have been a blog post.
- sidewinder128 6y agoI cancel my twitter/FB/Google etc, all that sns no-sense so I cannot read it, I think is a good thing.
- globular-toast 6y agoThe most addictive games are those with a small marginal commitment of playing another game. It's incredibly easy to rack up hours on such games, yet if you asked people if they were prepared to commit hours to the game they'd be likely to say no. Twitter is even worse. Not only does it not make the time commitment clear up front, the tweets are short enough that you read them automatically. Then you're hooked into the doom scroll as you keep automatically reading one after another. As a writer it means you don't need to bother with structure and other classical writing skills to keep your reader interested. You can just write disconnected chunks of text and rely on twitter to keep them interested.
- sundarurfriend 6y agoI too find this type of posting horrible, and avoid opening these generally. Part of my problem is specifically with Twitter UI and slow load times though, so when I do feel like it's worth opening, I use a Nitter redirect addon in my browser. Loading via Nitter instances is much faster for me, and works without even needing Javascript.
- jamra 6y agoThe last comment stated that Amazon recently spent a lot of effort ripping out Oracle. I would be interested in knowing how that was done and how much better things got afterwards.
- blinkingled 6y agoI don't know how much things got better from performance standpoint - Oracle is pretty good on that front - but they built their own Aurora database adding all the missing features to it and then migrating to it. (Bunch of blog posts on Aurora look it up.) Knowing what I know about Oracle licensing it must have gone pretty well on the money front!
- akhilcacharya 6y agoOne way things got better is they just migrated to pre-existing, externally available AWS services for many applications. Being able to sell them to Amazon teams at internal cost, getting performance and scale benefits and being able to use AWS primitives for orchestration is a major win. Here's a PR piece about it: https://aws.amazon.com/blogs/aws/migration-complete-amazons-consumer-business-just-turned-off-its-final-oracle-database/ https://aws.amazon.com/blogs/aws/migration-complete-amazons-...
- SmooL 6y agoFairly certain they're alluding to Amazon's company wide effort to get off of oracle databases, with most teams opting to use dynamodb instead. AFAIK it took about ~4 years. Source: interned / worked at amazon for a bit a few years back
- kablow 6y agoIn at least a few orgs I've seen the switch was to RDS (usually postgres) instead of dynamodb because they couldn't justify an entire redesign of the schema at the same time as the switch. It was a huge effort with a lot of late nights especially at the very end of the cutover.
- mxz3000 6y agoThey definitely didn't replace oracle with dynamo, those are very different beasts and would require complete redesigns of the migrated service. RDS sounds much more appropriate/realistic.
- blinkingled 6y agoSwitching to Linux in 2000 for something as busy as Amazon.com was a really ballsy move. I remember fighting kernel panics and hangs under load on RH7 - java workloads. This was pre RMAP VM and I vaguely remember the JVM was able to trigger Linux VM scalability issues due large number of anonymous page mappings. For all the money they were charging Sun did really put lot of engineering effort into Solaris and SPARC.
- bcrl 6y agoWe (the Linux kernel community) put a lot of work into scalability back then. One time we delayed a Red Hat release several weeks due to a persistent bit flip on an NFS filesystem on one of our stress tests that we thought was a kernel bug. It ultimately turned out to be a broken Cisco switch that was happily fixing up the CRC and checksums on the NFS packets it was bit flipping.
- blinkingled 6y agoOf course. Sun was ahead of the curve in OS scalability and SMP hardware departments and for some time Solaris was still the best OS to run databases and Java.
- bcrl 6y agoSun also made some pretty awesome x86 servers. It's sad that so many of the vendors left standing today have such crappy IPMI implementations.
- Bluecobra 6y agoI used to work at a shop that had hundreds of X4100's running x86 Solaris 10. It was a pleasure to work those hosts. Solaris had some really cool stuff like ZFS, dtrace, Zones/Containers, SMF, etc.
- yetanotherme 6y ago
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- vp8989 6y agoThat's funny because AWS definitely feels like the IBM or Sun of this current era. I wonder what comes along next or if AWS is the "end of history".
- Ericson2314 6y agoAWS is not the end of history. The hardware arch is still completely insane PC lineage too much, and now that electricity not hardware costs predominate, the calculus is has shifted tons.
- 0xbadcafebee 6y agoAWS is in their 1970's IBM phase. Riding high, wealthy, good reputation, not much real competition. In 10 years they will be knocked on their heels as they fail to adjust to a new industry change. My suspicion is that eventually AWS will become the "mainframes" of tech, and a new software+hardware paradigm will make all their services obsolete and their hardware too expensive. My money's on the return of store-and-forward communications. Once your watch has as much power and storage as a SunFire T2000, and every IoT device can store terabytes of data on gigabit networks, who the hell needs redundant servers?
- pjmlp 6y agoCloud computing is the mainframes of 21st century, with upgraded terminals, so it suits them.
- cthalupa 6y agoFrom replies to that thread, it looks like there are multiple errors. One reply is from one of the original engineers working on EC2 that said this swapover had nothing to do with AWS and it's origins, and another reply is from a former distinguished engineer stating that they swapped from compaq/digital tru64 alpha servers, not sun.
- mkl 6y agoAnd Linux was released in 1991, not 1994.
- gizmodo59 6y ago1.0 was 1994
- darksaints 6y agoSometimes there are a lot of people that experience part of the story that there can be multiple versions of the truth, each seemingly different, but all still fitting in with a larger narrative. In 2012 I joined Amazon in a a small data analytics org within the supply chain. We were tasked with reducing split shipments: multiple item orders that could not ship out on a single box. The top reason for splitting a shipment was because we simply didn't have the right combination of items in a single fulfillment center. By the time I had gotten there, my manager had already successfully implemented the first transshipment network, moving items from one warehouse to another so they could ship out with the right combination of items and reduce a split shipment. But by then we were reaching diminishing returns on transshipment, and splits were still rising nationwide, and I was given the chance to provide analysis and new insights. I probably ran a million analyses that year, but one of the most salient was that the major reason for splitting shipments was because we we sold so few of one of the items that it didn't make sense to keep more than one or two in stock nationwide. Those types of tail items were typically stocked in one of three fulfillment centers, the largest of the fulfillment centers in three regions of the US. And the number of orders getting split shipments between those three fulfillment centers was massive...more than enough to cover the cost of daily cargo plane transshipments between the three fulfillment centers. I ended up leaving that team and moving on, eventually leaving Amazon completely. Right about the time I left, Amazon made a huge anouncement: Amazon Prime Air (eventually renamed Amazon Air to distinguish between the drone delivery idea). The press releases made it sound like they were launching it to deliver packages nationwide, but a quick call to my former colleague confirmed that upon launch, the only items they were moving was unpackaged inventory ... cargo plane transshipment, as my analyses had pushed for a few years earlier. Since then, they've expanded to actually moving customer shipments, but the service was initially entirely justified based on an analysis of split shipments I had done years earlier. I say this because all humans like telling stories about themselves and the oversized contribution they had on something that made it big. It's cool, and it makes us feel important. But I was hardly the only person that worked on that project. There were likely dozens of others who were pushing for cargo planes for different reasons and maybe the transshipment story was enough to tip it over the edge. There were many more who bought into a crazy idea really early and came to own it, at least far more than someone who did a throwaway analysis years earlier. And they all probably have different versions of the same story. And they can all be true simultaneously, at least true enough to matter. Because none of us have a perfect recollection of the past...we all have a history written into our minds that is colored by the experience that we lived.
- motyar 6y agoWe feel same as amazon felt for Sun, Thinking about switching to fast and cheaper alternatives, or self host it.
- gscott 6y agoVPS servers are an excellent deal get a big one then run containers on it.
- motyar 6y agoYes, tried that last night. Moved code to VPS. Its nodejs app, what are advantage or running in containers?
- yetanotherme 6y agoUntil you need them, none. They sort of become self evident and you'll know when you're in the market for them. For now, don't waste time on premature optimization.
- nabla9 6y agoIt took 10 years for Amazon stock to recover back to dot-com-bubble levels.
- mark-r 6y agoI think that's more a comment on the insane dot-com bubble era valuations than anything else.
- rconti 6y agoNo doubt Solaris on SPARC was more reliable (particularly on higher-performance boxes) than Linux on x86 at the time, but tons of decent-sized hosting-type companies were running on Linux in the late 90s, and I worked at one. Obviously at Amazon's scale this was a massive migration, and giving up the support of Sun would be hard, but, hell, Google was launched on Linux at the time too. That said, I was supporting Sparc Solaris through the late 2000s and the Oracle workloads were the last thing to move to Linux most places. The sheer power of the Sun boxes, along with the single-throat-to-choke was fairly unbeatable. No hardware vendor to look down their nose at you for using a "hobbyist" OS and imply that the problem must be at the Operating System level. And, of course, you couldn't really replace those huge Sun Fire 6800 type servers with Linux.
- sumanthvepa 6y agoOkay. I was at Amazon too in that time frame, and I don't recall the Sun to Linux transition to be all that big a deal. Amazon was always at that time facing challenges on every front, the dot-com bubble breaking etc. There was a large build out of distribution centres around this time that was very expensive. This was just one more of the challenges they faced. I may not have been senior enough to be privy to all the details, but I don't think this particular migration brought the company to near bankruptcy. That's a stretch. I think the big migration was the database, and it took time, and Oracle was having some difficulties with running on Linux. But we were already using Linux boxes on our desktops since 1999. Webservers had switched to Linux around 1999. And migrating core code base which mostly C/C++ with Java starting to appear to Linux was mostly a challenge for the infrastructure teams and one of those routine large projects that every company has. I don't recall anybody talking of bankruptcy for this reason.
- geoduck14 6y agoPlease share stories of what early Amazon was like. Did you realize you were building a massive company at the time?
- sumanthvepa 6y agoAmazon was already a public company and pretty big that time. But I don't think people like me realised what big could mean 20 years into the future.
- chihuahua 6y agoI worked there for a few years in the early 2000s and it seemed like such an unremarkable company that wasn't going to go anywhere. The stock was always around $20 and whenever it went up, Bezos usually said something that investors didn't like and drove down the stock price (free shipping, search inside the book, etc). Then there was the Segway deal where I amused myself by checking the orders database to see how many they sold (because the numbers were so small) If you told me back then that the stock was going to $3000 some day, I would have stuck around for longer.
- mhh__ 6y agoThey were all but dead (AFAIK) by the time I was was born, so the old Unixes and RISCs all have a ghostly feel to them to me at least. It's quite strange reading many now-ageing compiler texts talking about 386 as a wacky ISA soon to die out. I really want an Alpha box to play with, partly out of curiosity but partly to feel like a real man programming with next to no memory consistency. Although they didn't help themselves it does seem like the probably-ending dominance of X86 has hurt the industry up til now. edit: It's a pretty crap ISA, controversial?
- yjftsjthsd-h 6y ago> the old Unixes and RISCs all have a ghostly feel to them to me at least. It's quite strange reading many now-ageing compiler texts talking about 386 as a wacky ISA soon to die out. Illumos and the BSDs seem to be doing okay, and ARM is huge. The x86 family didn't die out but it is wacky. > I really want an Alpha box to play with, partly out of curiosity but partly to feel like a real man programming with next to no memory consistency. I'm pretty sure ARM will give you that.
- KMag 6y agoRight out of school (early 2000s), I did network modelling consulting. My main client bought a Sunfire V1280 box (12 CPUs, and the server room guys hated me for the amount of power it drew/heat it put out) to run network simulations. As I remember, the main two advantages SPARC and POWER systems being sold at that time over x86 were (1) reliability and (2) memory / I/O bandwidth. I tried to look up who first said something along the lines of "A supercomuter is a tool for turning a compute-bound problem into an I/O-bound problem" and all I could find was an ArsTechnica article referencing it as an old joke. I thought it was an old joke by someone of the stature of Cray or Amdahl, but maybe that's apocryphal. In any case, our network simulations attempted to perform a min-cut (using number of packets as the cost metric) to partition simulation nodes among threads, run one thread per core, and pin a thread to each core. With a network simulation, though, as you can imagine, the problem was usually bound by memory bandwidth. Also, the client was a defense contractor, and the 400k+ USD box was an artefact of "use it or lose it" budgeting. If they didn't spend all of their budget by December 31st, the group's budget would be reduced the following year. In their case, the high cost of the box was a feature.
- random5634 6y agoAhh - govt budgeting - I've been there. What is a bit funny is after fighting for $1,000 during the year, some budget manager calls in a panic near year end - how fast can you spend $150K - on anything you want. Turns out - as Amazon has noticed with cheap stuff, whoever has stuff in stock and can ship quick gets the deal - price totally irrelevant. There was a while during the stimulus spending where politicians were I guess getting heat for not spending stimulus money fast enough, so the pressure to spend got pushed down big time. Every layer was trying to push spending out as fast as they could. For those not familiar with this area and wondering why a higher level agency would push spending rather than trying to save money? A lot of govt budgets between appropriation and final vendors are based on % of allocated spending. So a state agency will take 10%, a local agency will take 10%, and then it ends up in the hands of whoever does the work. Everyone above has built their budgets on all the money being spent. They've staffed for that. So if you show up and spend 50% of your allocation, now they only get 50% of their 10% and can be in a real jam, particularly if they have already spent their entire expected amount or committed to spend it (staff have been hired). It can be hard to re-budget amounts between vendors / recipients so the pressure on whoever didn't spend all their money can be intense, because it's messing up a whole chain of other budgets.
- donflamenco 6y agoHe is wrong and is corrected later on in that tweet. At that time, AMZN was mostly DEC Digital Unix. The DNS and mail servers were Linux in 97. AMZN started with SUNW (pre 97), but switched to Digital Unix because it was 64bit and could fit the catalog into RAM.
- protomyth 6y agoThis tweet: Peter Vosshall https://mobile.twitter.com/PeterVosshall/status/1347697560249458689 https://mobile.twitter.com/PeterVosshall/status/134769756024... No. The entire fleet was Compaq/Digital Tru64 Alpha servers in 2000 (and '99, and '98). Amazon did use Sun servers in the earliest days but a bad experience with Sun support caused us to switch vendors. So, the title is wrong.
- donflamenco 6y agoWell, like every internet company in 99, there was SUN servers. There was a lone sun workstation that printed some of the shipping docs in latex. I believe that was left by Paul Barton Davis. By early 97, the website (Netscape) and database (Oracle) ran on DEC Alpha hardware. Peter is wrong about switching to Digital Unix because Sun had bad support. The switch happened for 64bit reasons. There was almost a 24 hour outage of amazon.com because Digital Unix's AdvFS kept eating the oracle db files. Lots of crappy operating systems in the those days.
- ayewo 6y agoMultiple folks on Twitter hinted at inaccuracies in Dan Rose’s recollection of events at Amazon. In fact, when you mentioned Paul Davis, I realized I was looking through the comments to see him [1] point out these inaccuracies since he is known to hang out here on HN. 1: https://news.ycombinator.com/user?id=pauldavisthe1st https://news.ycombinator.com/user?id=pauldavisthe1st
- PaulDavisThe1st 6y agoI can't point out inaccuracies for that time period, since I left in January of 1996.
- etaioinshrdlu 6y ago"Sun servers were the most reliable so all internet co's used them back then, even though Sun's proprietary stack was expensive & sticky." A few things in the article start to rhyme a bit with where NVIDIA is at today. An expensive, proprietary, sticky stack. Purchased in large quantities by startups... An acquaintance who was at Sun and now NVIDIA tells me "Please don't be Sun... please don't be Sun!" Granted, NVIDIA is also in a great position in the gaming market, so they look pretty diversified and safe to me.
- rasz 6y agoNvidia was founded by SUN people after all.
- markhahn 6y agoLinux wasn't shocking or daring back then. Literally everyone could see that proprietary unixes (and their locked-in hardware) were doomed. "Attack of the killer micros" had already succeeded. Exactly which micro was still somewhat unsettled.
- desas 6y agoIt depends upon your environment, it wasn't clear to many people. I thought that proprietary unix was doomed when I started an internship at a bank's IT ops department in 2005. The seasoned Solaris admins I worked with had commissioned some Linux servers the year before in a non-prod setting and had written it off as a toy...
- pjmlp 6y agoIn 2005 Nokia was still using HP-UX as our main UNIX deployment platform, and doing a Solaris port of NetAct cluster software, GNU/Linux was indeed seen as a toy still.
- pjmlp 6y agoWhich could have been Windows as well, had Microsoft been serious with the POSIX subsystem.
- rmk 6y agoI remember Amazon hiring a lot of systems research people in 05-06. They were very keen on Xen, judging by the people they were hiring. I wonder if they still use Xen post their Citrix acquisition.
- jen20 6y agoEC2 was famously built on top of Xen, but as of 2017, new instance types are based on Nitro, which uses parts of KVM instead. Brendan Gregg wrote up a good history of this [1] (there may be an updated version somewhere, too). [1]: http://www.brendangregg.com/blog/2017-11-29/aws-ec2-virtualization-2017.html http://www.brendangregg.com/blog/2017-11-29/aws-ec2-virtuali...
- rmk 6y agoThat picture alone is a great lesson in how to convey a crap ton of information in a small amount of space. It was a great read, thank you!
- mjgs 6y agoGreat bit of history/context around cloud computing, even if there is a bit of dispute as to how big the impact was, it’s still super interesting.
- pjmlp 6y agoStop using Twitter for blog posts, by all means use medium if it must.
- kenned3 6y agoSeriously. Let me post this blog posting, 280 characters at a time.. that seems like a great, reader-friendly approach.
- Havoc 6y agohmmm...the comments suggest there may be some artistic license at play there.
- mrkramer 6y ago"I was at Amzn in 2000 when the internet bubble popped. Capital markets dried up & we were burning $1B/yr." "Amzn came within a few quarters of going bankrupt around this time." "Amzn nearly died in 2000-2003." Current Google's CFO Ruth Porat saved Amazon during dot-com crash [1] , she advised them to go to Europe to raise money otherwise they would face insolvency. [1] https://www.vox.com/new-money/2017/4/5/15190650/amazon-jeff-bezos-richest https://www.vox.com/new-money/2017/4/5/15190650/amazon-jeff-...
- martinald 6y agoThere's a lot of revisionist history around what AWS allowed. RackShack and other companies offered pretty cheap (started at $99/month IIRC) dedicated Linux servers which loads of startups used before AWS. There was also various virtual machine providers in the market. These articles make it sound like every company before AWS had to build their own datacenter or at least buy a million dollars worth of Sun hardware to put a website online.
- kazen44 6y agoHeck, old colleagues of mine have been doing "dedicated/shared hosting" for the better part of nearly 25 years. virtual private servers have existed for 20 decades+.
- vasco 6y agoI think 20 decades might be a bit of an exaggeration.
- breck 6y agoNo I actually remember reading a letter Lovelace wrote to Babbage about problems with chroot
- Misteur-Z 6y agoIBM mainframes virtual machines saying hello => "It is directly based on technology and concepts dating back to the 1960s" https://en.wikipedia.org/wiki/Z/VM https://en.wikipedia.org/wiki/Z/VM
- krallja 6y ago20 decades ago would be 1821 A.D., four decades before the First American Civil War.
- throwaway20148 6y agoThat’s what the CIA would have you believe.
- theanirudh 6y ago> Jeff started to think - we have all this excess server capacity for 46 weeks/year, why not rent it out to other companies? If Amazon rented out excess capacity after Nov/Dec, what did they do for next years Nov/Dec peak? Did they build up more capacity throughout the year and not rent it out?
- lizknope 6y ago> even though Sun's proprietary stack was expensive & sticky What is he referring to? I'm in the semiconductor industry and in the 1990's everyone had a Sun workstation on their desk. We had large 16 CPU Sun servers in the closet for bigger jobs. Since everything was either command line or X11 it was easy to set your DISPLAY variable and display things remotely. All of the EDA (Electronic Design Automation) tools ran on Sun / Solaris. Some of these tools from Cadence and Synopsys have list prices of over $1 million per license. Those big Sun monitors with DB13W3 connections were expensive. We started putting Linux / x86 boxes with 21" monitors on engineers desks and running programs remotely from the big Suns. We even started stacking the old desktop Sun workstations in the closet and running stuff remotely from them because people liked the bigger PC monitors. By 2000 the EDA software companies were recompiling their software for Linux. I talked to a few and they said it was a pretty easy recompile. x86 was getting to be faster and so much cheaper. We added a couple of -sun and -linux flags to the CAD wrappers. Everything was still connected over NFS with the same shell and Perl scripts. Honestly the transition was pretty seamless. When AMD released their first 64-bit chips we bought a lot of them and retired our final Suns that were only around for >4GB jobs.
- pavelevst 6y agoironically, but now AWS become such “commonly used but too expensive” solution for most of companies, which many of us already getting rid of
- williesleg 6y agoThey had to switch, how else can they dd those virtual machines and spin them up elsewhere and steal everything?
- aritmo 6y agoThere is a common typo in the tweet thread, it's *vicious circle*, not viscus circle. Ref: https://en.wikipedia.org/wiki/Virtuous_circle_and_vicious_circle https://en.wikipedia.org/wiki/Virtuous_circle_and_vicious_ci...
- draw_down 6y agoCome on
- hermanradtke 6y agoA different version of how EC2 came to be: http://blog.b3k.us/2009/01/25/ec2-origins.html http://blog.b3k.us/2009/01/25/ec2-origins.html
- tyingq 6y agoI'd argue they went a bit early. Pre x64, so they would have been moving from 64 to 32 bit. And Linux, at the time, had a variety of issues at scale with kernel panics, leaks, etc.
- jakub_g 6y agoAnother story from same author from few months ago where he recounts yearly Xmas spikes in early AMZN years where everyone including Bezos was packing boxes to meet the demand: https://mobile.twitter.com/danrose999/status/1304896586086928384 https://mobile.twitter.com/danrose999/status/130489658608692...
- Tistel 6y agoSorry if this has been asked already. Out of curiosity, what did they replace oracle with? Postgres, MySQL, both? Or did the roll their own?
- hacker_newz 6y agoInteresting that this thread seems to attribute a lot of the early AWS decisions directly to Jeff Bezos when everything I've read before indicates it was a collaborative effort including Andy Jassy. https://techcrunch.com/2016/07/02/andy-jassys-brief-history-of-the-genesis-of-aws/ https://techcrunch.com/2016/07/02/andy-jassys-brief-history-...
- zhubert 6y agoWell this was an interesting thread to see pop up. Hi, I'm Zack, I was a Sr. Unix Administrator at AMZN in 1999 and worked alongside very talented folks like snovotny, lamont, yvette, grabatin, gborle, jamison, craig, and so many others. The responses from Benjamin Black and Peter Voshall are correct. We definitely were on DEC Tru64 at this time. Sun was running the big databases like ACB. I recall worries that obidos might not be able to build in a few months time so the engineer with the little corgi (Erik?) spiked out a linux build and then it was linux pizza boxes as quickly as we could build them. We built CMF and other things to handle mass provisioning but it was chaotic for quite a while. I don't recall anyone talking about what would later become AWS in those days.
- alexhutcheson 6y ago> I recall worries that obidos might not be able to build in a few months time What was going to cause this?
- jgalt212 6y ago? Why should a business in 2000 have to build its own datacenter? But in 2020, most small/medium sized business could be run on two-ish beefy boxes. With a cloudflare, or similiar, firewall there simply is no need to build your own or rent a datacenter.
- marcuskaz 6y agoI worked at ETRADE around the same time and led the migration from Sun to Linux on the software side, switching everything to Apache was once a radical idea. We switched to IBM machines and not HP, a Sun server cost around $250k and the equivalent Linux server was $5k and outperformed the Sun machines. It still was considered risky by CTOs. During the dotcom boom there was huge competition for ordering Sun machines and it was difficult to get enough, we were competeting with eBay to get our hands on machines. During the crash, we went back to eBay as a seller and couldn't off load all the old Sun machines. Here's an article from the time: https://www.baselinemag.com/c/a/Projects-Enterprise-Planning/ETrade-Bets-Big-on-Linux https://www.baselinemag.com/c/a/Projects-Enterprise-Planning...