InfoQ Homepage Infrastructure Content on InfoQ
-
Data Infrastructure @ LinkedIn
Sid Anand presents the architecture set in place at LinkedIn and the data infrastructure running Java and Scala apps on top of Oracle, Voldemort, DataBus and Kafka.
-
Scaling Devops - Breaking Down the Barriers between Development and IT Operations
Jez Humble discusses how to deal with risk management, regulation compliance, ITIL, audit requirements in a large organization that intends to adopt devops.
-
Dynamo Is Not Just for Datastores
Susan Potter discusses Dynamo, Riak, distribution, consistency and fault tolerance, along with techniques and an example for building an application with riak_core.
-
Architecting in the Gaps
Eoin Woods suggests creating the architecture of a system by discovering the interactions between the components and focusing on the boundaries, helping with defining the interfaces and interactions.
-
Techniques for Scaling the Netflix API
Daniel Jacobson covers the history of Netflix’s APIs, adaptation for the cloud, development and testing, resiliency, and the future of their APIs.
-
Uptime in High Volume Messaging Systems — Lessons Learned
Erik Onnen shares lessons learned while designing the architecture, implementing it, and releasing it into operations at Urban Airship, providing hosting for mobile services.
-
Architecting for Failure at the Guardian.co.uk
Michael Brunton-Spall talks about various types of system failure that can happen, sharing the lessons learned at the Guardian and measures taken to prevent and mitigate failure.
-
Timelines @ Twitter
Arya Asemanfar presents Twitter’s timeline architecture, the entire sequence of steps a tweet goes through until it reaches the timeline of each user following the person who tweeted.
-
Free Pizza! A Glimpse Inside eCommerce at Domino’s Pizza
Bill Heitzeg shares the lessons learned and the process of recreating a new e-commerce platform and website for Domino’s Pizza.
-
AMQP 1.0 Core Features
Robert Godfrey discusses the requirements set at AMQP’s foundation: Applicability, Reliability, Fidelity, Interoperability, Manageability, Ubiquity, explaining how AMQP was designed for the future.
-
Architecture Without an End State
Michael Nygard outlines 8 rules for dealing with complex systems: Embrace Plurality, Contextualize Downstream, Beware Grandiosity, Decentralize, Isolate Failure Domains, Data Outlives Applications ...
-
Resilient Response In Complex Systems
John Allspaw discusses pitfalls to be avoided while troubleshooting failed systems, comparing web operations at scale with practices in aviation and nuclear power industries.