Example
For the last few months I've been programming a system in Go, so I'm always on the lookout for information to feed my confirmation bias. An opportunity popped up when Iron.io wrote about their experience using Go to rewrite IronWorker, their ever busy job execution
humor
I am in no way a music expert, but when I listen to Symphony No. 4 by Charles Ives, I imagine it's what a complex software/hardware system might sound like if we could hear its inner workings. Ives uses a lot of riotously competing rhythms in this
Strategy
We talked about 42 Monster Problems That Attack As Loads Increase. And in The Aggregation Collection we talked about the value of prioritizing work and making smart queues as a way of absorbing and not reflecting traffic spikes. Now we move on to our next batch of strategies where the
hot links
Hey, it's HighScalability time: * Quotable Quotes: * @ibogost: Disabling features of SimCity due to ineffective central infrastructure is probably the most realistic simulation of the modern city. * antirez: The point is simply to show how SSDs can't be considered, currently, as a bit slower version of memory.
Paper
In Algorithm Design for Performance Aware VM Consolidation we learn some shocking facts (gambling in Casablanca?): * Average server utilization in many data centers is low, estimated between 5% and 15%. This is wasteful because an idle server often consumes more than 50% of peak power. * Surely that's just
Strategy
What good are problems without solutions? In 42 Monster Problems That Attack As Loads Increase we talked about problems. In this first post (OK, there was an earlier post, but I'm doing some reorganizing), we'll cover what I call aggregation strategies. Keep in mind these are
sponsored post
Who's Hiring? * Fitbit is hiring a Site Operations Lead to help us on our mission to make the world a healthier place! Fitbit's wearable fitness devices are worn by people across the world, each syncing with the web site, wirelessly and automatically, every 15 minutes. Join
humor
Listen up all you IT people...NoSQL, it's the rage now, so turn the page now and boost your stack...Hey, mighty people...Go, go, go, hey, hey, hey, hey, hey, hey...Go NoSQL style... I for one feel both edified and entertained...can't wait for
Strategy
We talked about 42 Monster Problems That Attack As Loads Increase. Here are a few ways you can defend yourself, secrets revealed by scaling masters across the ages. Note that these are low level programming level moves, not large architecture type strategies. Use Resources Proportional To a Fixed Limit This
hot links
Hey, it's HighScalability time: Unfortunately with Delicious still down access to all my lovingly curated links is out. But the show must go on... * Quotable Quotes: * @muratdemirbas: In the cloudcomputing webservices domain antifragility= elastic scalability + network effect * @SQLPerfTips: More hardware won't solve response time problems. Proper
Strategy
For solutions take a look at: 7 Life Saving Scalability Defenses Against Load Monster Attacks. This is a look at all the bad things that can happen to your carefully crafted program as loads increase: all hell breaks lose. Sure, you can scale out or scale up, but you can
Example
Should you use PaaS for your next project? Often the answer is no because you want control, but here's an example from SongPop showing why the promise of PaaS is not passé. SongPop was able to autoscale to 60 million users, 1 million daily active users, deliver 17