How Team Obama’s tech efficiency left Romney IT in dust | Ars Technica
The web-app dev and ops best practices used by the Obama campaign’s tech team. Some key tools: Puppet, EC2, Asgard, Cacti, Opsview, StatsD, Graphite, Seyren, Route53, Loggly, etc.
Tumblr Architecture – 15 Billion Page Views A Month And Harder To Scale Than Twitter
Buckets of details on Tumblr’s innards. fans of Finagle and Kafka, notably
John Carmack’s .plan update from 10/14/98
John Carmack presciently defines the benefits of an event sourcing architecture in 1998, as a key part of Quake 3’s design:
“The key point: Journaling of time along with other inputs turns a realtime application into a batch process, with all the attendant benefits for quality control and debugging. These problems, and many more, just go away. With a full input trace, you can accurately restart the session and play back to any point (conditional breakpoint on a frame number), or let a session play back at an arbitrarily degraded speed, but cover exactly the same code paths.”
(This was the first time I’d heard of the concept, at least.)(tags: john-carmack design software coding event-sourcing events quake-3)