It's HighScalability Time (Good luck today):
A Friday the 13th Postmorterama:
James Hamilton with some high powered perspective on the report for the Fukushima Nuclear Accident. Apparently they haven't heard of the blameless post-mortem. Lots of interesting stuff, but this is a potentially disaster saving general lesson learned: operators can't figure out what is happening or take appropriate action without detailed visibility into the state of the system.
* James Hamilton gives an interesting spin on the importance of reducing latency .
* Tommy Jarnac gives three best practices for managing your Django settings in development and production environments.
* VC Chip Hazard describes ten ways companies can drive developer adoption .
* Nikos Lianeris gives a tutorial on how to configure . compression with ehcache
* Doug Grismore describes a few useful Amazonperformance …
Submitted for your scaling pleasure:
…processors. Why can't they operate at higher temperatures? This is the proposition addressed by James Hamilton in Exploring the Limits of and Datacenter Knowledge in Temprature What's Next? Hotter . with ‘ Pedals'
Quotable Quotes for 200:
@ jreichhold : One thing working at teaches me daily is that all scale is relative. What seemed impossible last year is now the …
…This is a wonderfully written and accessible paper, chocked full of useful and interesting details. James Hamilton wrote an excellent summary of the paper in Google Megastore: The . There are also a few useful threads in Behind GAE that go into some more details about how it works, costs, and performance (the original announcement , performance comparison ).
Some Megastore highlights:
Eating turkey all weekend and wondering what you might have missed?
James Hamilton on why "all you have learned about disks so far is probably wrong" in Availability in Globally Distributed Storage . It turns out for the same reason our financial systems melt down: black swans . The world is predictably unpredictable. Murat Demirbas also has a good post on the same research paper .
Erlang Factory: Andy Gross: Distributed by Martin J. Logan. Great overview of architecting distributed systems in Erlang. Covers what you want and don't want in a distributed system and how to compromise … In Operation: Patterns and Pitfalls
Deferred On and Deploying Internet-Scale Services:is a technique where deleted items are marked as deleted but not garbage collected until some days or preferably weeks later . James Hamilton talks describes this strategy in his classic
Never delete anything. Just mark it deleted. When new data comes in, record the requests on the way. Keep a rolling two week (or more) history of all changes to help recover from software or administrative errors. If someone …