Hacker News new | past | comments | ask | show | jobs | submit login

Just because the product is big doesn't mean its a monolithic codebase. Amazon is powered by a lot of different pieces. Decoupling let's you keep the pieces small and yet grow and scale to huge sizes.



Amazon is powered by an army of engineers coming to the rescue when something fails again.


It's also a maintenance nightmare. A LOT of that code is terrible, there's a lot of tight coupling, and a heavy reliance on developers with pagers to keep the mess operating.

There's a reason that they have such insane turnover so few people who stick around after they collect their signing bonuses...


thanks, that's some interesting information. that does strengthen the OP's case.

Loose coupling should be possible but a rarely seen feat I reckon for websites of this scale.

I wonder how "loosely" coupled and well architected the 2.0 sites are like digg and facebook?


You can read about facebook's architecture at highscalability and other sites of that ilk.


Are you speaking from experience?


How'd you guess?


lucky guess :-)


ACM has a great interview with Werner Vogels, Amazon's CTO, about how their platform is structured.

http://queue.acm.org/detail.cfm?id=1142065




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: