28 Feb '14, 2am

Scalable System Design Patterns: < A great infographic-like review of most common distributed compu…

Scalable System Design Patterns: < A great infographic-like review of most common distributed compu…

I really like this general idea, but I think that what is missing here is a description of how each pattern handles failure . Much of the difference between a system which is theoretically scalable and one which is scalable in the real world is that the real-world scalable system can cope with the failure of individual components without knocking over the entire system. James Hamilton once wrote: "Once the service has scaled beyond 10,000 servers and 50,000 disks, failures will occur multiple times a day. If a hardware failure requires any immediate administrative action, the service simply won’t scale cost-effectively and reliably. The entire service must be capable of surviving failure without human administrative interaction. Failure recovery must be a very simple path and that path must be tested frequently."

Full article: http://horicky.blogspot.com/2010/10/scalable-system-desig...

Tweets

RAD: Great Design, Coffee, And Vietnamese Food In Auckland

RAD: Great Design, Coffee, And Vietnamese Food ...

sprudge.com 28 Feb '14, 9pm

RAD Mt. Eden is an exciting new entrant into the Auckland cafe scene. It can be hard to stand out amongst all the interest...

Confuse the Birds with this Daylight Simulation System

Confuse the Birds with this Daylight Simulation...

hackaday.com 26 Feb '14, 9am

Hackers love a challenge. So when [Patrick's] father-in-law asked him to look into a daylight simulation system for his bi...