InfoQ Homepage Failure Content on InfoQ
-
Entirely Predictable Failures
Poul-Henning Kamp considers that if developers are not getting better, we are going to repeat many of the major IT project failures. He exemplifies with major Denmark project failures.
/presentations/Predictable-Failures/en/smallimage/Poul.JPG)
-
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.
/presentations/Architecting-for-Failure-at-the-Guardian/en/smallimage/Michael.JPG)
-
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.
/presentations/Resilient-Response-In-Complex-Systems/en/smallimage/John.JPG)
-
On Distributed Failures (and handling them with Doozer)
Blake Mizerany presents various ways that can lead to system failure in distributed systems and how to recover using Doozer, a highly available, consistent data store.
/presentations/On-Distributed-Failures/en/smallimage/Blake.JPG)
-
Things Break, Riak Bends
Justin Sheehy talks about failure and the need to prepare for it, giving some real life examples along with techniques implemented in Riak to make it resilient to faults.
/presentations/Things-Break-Riak-Bends/en/smallimage/Justin.JPG)
-
Everything I've Ever Learned, I Learned from Failure
Robert Myers talks about the role played by failure in Agile development, sharing a number of Lean and Agile practices helping to embrace failure and showing how to interpret the feedback received.
/presentations/I-Learned-from-Failure/en/smallimage/Robert.JPG)
-
Failures and Successes with Reuse
Herbjörn Wilhelmsen discusses the reasons why an SOA project failed while trying to reuse existing resources, and how it succeeded later starting from the same business case with reuse in mind.
/presentations/Failures-and-Successes-Reuse/en/smallimage/Herb.JPG)
-
Embracing Concurrency At Scale
Justin Sheehy explains the principles behind concurrent distributed systems: no global state, no ACID but rather BASE, no RPC but protocols over APIs, prepare for failure, degradation, measurement.
/presentations/Embracing-Concurrency-At-Scale/en/smallimage/10-mar-embracingconcurrency.JPG)
-
Failure Comes in Flavors - Stability Anti-patterns
Michael Nygard encourages us to have a failure oriented mindset. He presents many anti-patterns leading to systems instability and failure, accompanied by design patterns that should be used instead.
/presentations/Stability-Anti-patterns-Michael-Nygard/en/smallimage/MNygard.jpg)
-
10 Ways to Screw Up with Scrum and XP
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
/presentations/Fail-Scrum-Henrik-Kniberg/en/smallimage/HKniberg.jpg)
-
"We Suck Less!" Is Not Enough
David Douglas and Robin Dymond discuss about companies adopting Agile, but don't go all the way, resulting in failure and rejection of it, and predictably having a negative impact on Agile's future.
/presentations/We-Suck-Less-Douglas-Dymond/en/smallimage/DouglasDymond.jpg)