BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations Architecture Without an End State

Architecture Without an End State

Bookmarks
40:17

Summary

Michael Nygard outlines 8 rules for dealing with complex systems: Embrace Plurality, Contextualize Downstream, Beware Grandiosity, Decentralize, Isolate Failure Domains, Data Outlives Applications, Applications Outlive Integrations, Increase Discoverability.

Bio

Michael Nygard strives to raise the bar and ease the pain for developers across the country. 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.

About the conference

GOTO Aarhus is the enterprise software development conference designed for team leads, architects, and project management and is organized by developers, for developers. As software developers and architects ourselves, we wanted to craft the ultimate conference. The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community, staged in an intimate environment needed to support as much learning and networking as possible.http://gotocon.com/

Recorded at:

Apr 20, 2012

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • 5 stars

    by Olivier Gourment,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Why can't you vote on a talk?
    "all models are wrong. Some are useful. Utility is contextual"
    One of the many, many pieces of wisdom delivered in this talk.
    It might take a few more years for many architects and CIOs to grasp the messages, but..
    Thank you Michael!

  • 3 year plan

    by Jez Humble,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    It's always a 3 year plan because the tenure of most VPs is 2 years

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT