<<< Previous speaker next speaker >>>

Michael T. Nygard, Author of "Release It!"

 Michael T.  Nygard

Michael Nygard strives to raise the bar and ease the pain for developers across the country. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. Michael has spent the better part of 20 years learning what it means to be a professional programmer who cares about art, quality, and craft. He's always ready to spend time with other developers who are fully engaged and devoted to their work--the "wide awake" developers. KatFu says HI. On the flip side, he cannot abide apathy or wasted potential. Michael has been a professional programmer and architect for nearly 20 years. During that time, he has delivered running systems to the U. S. Government, the military, banking, finance, agriculture, and retail industries. More often than not, Michael has lived with the systems he built. This experience with the real world of operations changed his views about software architecture and development forever.

He worked through the birth and infancy of a Tier 1 retail site and has often served as "roving troubleshooter" for other online businesses. These experiences give him a unique perspective on building software for high performance and high reliability in the face of an actively hostile environment.

Most recently, Michael wrote "Release It! Design and Deploy Production-Ready Software", a book that realizes many of his thoughts about building software that does more than just pass QA, it survives the real world. Michael previously wrote numerous articles and editorials, spoke at Comdex, and co-authored one of the early Java books.

Presentation: "When the Fur Flies: Dev and Ops Cooperation when the Worst Happens"

Time: Wednesday 16:50 - 17:50

Location: Cornell Room

Abstract: There's nothing like a crisis to remove artificial barriers. In this session, Michael will present an experience report about development and operations coming together after a failed launch. Aside from the fun of sharing war stories and comparing scars, what can we learn about climbing out of a crater after the worst has already happened? Can we capture the special magic of a firefighting mission during more sedate times? Beyond all of that, come find out how to stay out of the crater to begin with.

Devops, velocity, disaster, crisis, organization, architecture

Target Audience: Developers, development managers, architects

Presentation: "Where to put data"

Track: NoSQL

Time: Thursday 12:05 - 13:05

Location: Stanford Room

Abstract: It used to be an easy question. "Where should I store my data?" In the relational database, obviously. Well, not any more. These days, we've got relational databases, graph databases, column databases, key-value databases, and caches out the wazoo.

Each of these technologies is good at some things and bad at others. We can use them in combination to make highly scalable, agile, high performance applications. It would help, however, if we had some heuristics about our architecture. We can apply some principles, practices, and patterns to help decide how to use each of these technologies.

This talk probably won't please either the gray-suited relational conservatives or starry-eyes NoSQL revolutionaries. It might, however, help you sort out where to put your data.