GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes

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

Michael T. Nygard

Biography: 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. Living with systems in production taught Michael about the importance of operations and writing production-ready software. Highly-available, highly-scalable commerce systems are his forte.

Michael has written and co-authored several books, including "97 Things Every Software Architect Should Know" and the best seller "Release It!", a book about building software that survives the real world.

Book: Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers)

Presentation: Chef in the Cloud and On the Ground

Track: DevOps / Time: Monday 10:20 - 11:10 / Location: Rytmisk Sal, Musikhuset

Chef is one of the "Infrastructure as Code" configuration management systems. It lets you automate the setup and deployment of your environments: including physical machines and at least two flavors of virtual machine.

This talk introduces Chef and shows how you can use it in your data center, then turn around and use exactly the same cookbooks in a cloud. Whether you're migrating into the cloud or using it for dev and test environments, exploiting a common base of automation will make your system a joy to manage.

Presentation: Architecture Without an End State

Track: So you think you're an architect / Time: Wednesday 13:20 - 14:10 / Location: Store Sal, Musikhuset

You've seen them. You've probably made one: The architecture vision diagrams. The block diagrams, the message bus topologies... How many of these diagrams ever actually get built?

We never really finish constructing one of these grand visions before something interferes. Maybe it's a merger or acquisition. Maybe your company has a "regime change". (After all, the average tenure of a CIO is down to 18 months!)

The "end state" vision never gets built. Instead, we need to focus on how to flex and change, incorporating new technology, new principles, new business models, and even the last generation's legacy. Call it agile architecture, or meta-architecture, or "how I learned to love laminated stucco." It's architecture without an end state.