Application Architecture Guide

From Guidance Share

(Difference between revisions)
Jump to: navigation, search
Revision as of 22:43, 25 April 2009 (edit)
JD (Talk | contribs)

← Previous diff
Current revision (02:44, 22 January 2010) (edit)
JD (Talk | contribs)

 
Line 1: Line 1:
-- J.D. Meier, Alex Homer, David Hill, Jason Taylor, Prashant Bansode, Lonnie Wall, Rob Boucher Jr, Akshay Bogawat.+<em style="margin:0;background-color:#cedff2;font-family:sans-serif;border:1px solid #a3b0bf;text-align:center;color:#000;padding:0.2em 0.4em;">
 +Note - The patterns & practices Microsoft Application Architecture Guide, 2nd Edition is now live at http://msdn.microsoft.com/en-us/library/dd673617.aspx.
 +</em>
 + 
 +- J.D. Meier, Alex Homer, David Hill, Jason Taylor, Prashant Bansode, Lonnie Wall, Rob Boucher Jr, Akshay Bogawat.
Line 63: Line 67:
* [[Application Architecture Guide - Cheat Sheet - Workflow Technology Matrix | Cheat Sheet - Workflow Technology Matrix]] * [[Application Architecture Guide - Cheat Sheet - Workflow Technology Matrix | Cheat Sheet - Workflow Technology Matrix]]
* [[Application Architecture Guide - Cheat Sheet - Integration Technology Matrix | Cheat Sheet - Integration Technology Matrix]] * [[Application Architecture Guide - Cheat Sheet - Integration Technology Matrix | Cheat Sheet - Integration Technology Matrix]]
-  
- +__NOTOC__ __NOEDITSECTION__
-== Chapters ==+
-The following overview shows you how to execute the agile architecture method:+
-* [[Agile Architecture Method Explained - Introduction | Introduction]]+
-* [[Agile Architecture Method Explained - Chapter 1 - Agile Architecture Method | Chapter 1 - Agile Architecture Method]]+
-* [[Agile Architecture Method Explained - Chapter 2 - Step 1: Identify Architecture Objectives | Chapter 2 - Step 1: Identify Architecture Objectives]]+
-* [[Agile Architecture Method Explained - Chapter 3 - Step 2: Identify Key Scenarios | Chapter 3 - Step 2: Identify Key Scenarios]]+
-* [[Agile Architecture Method Explained - Chapter 4 - Step 3: Application Overview | Chapter 4 - Step 3: Application Overview]]+
-* [[Agile Architecture Method Explained - Chapter 5 - Step 4: Key Hot Spots | Chapter 5 - Step 4: Key Hot Spots]]+
-* [[Agile Architecture Method Explained - Chapter 6 - Step 5: Candidate Solutions | Chapter 6 - Step 5: Candidate Solutions]]+
-* [[Agile Architecture Method Explained - Chapter 7 - Reviewing Your Architecture | Chapter 7 - Reviewing Your Architecture]]+
-* [[Agile Architecture Method Explained - Chapter 8 - Communicating Your Architecture | Chapter 8 - Communicating Your Architecture]]+

Current revision

Note - The patterns & practices Microsoft Application Architecture Guide, 2nd Edition is now live at http://msdn.microsoft.com/en-us/library/dd673617.aspx.

- J.D. Meier, Alex Homer, David Hill, Jason Taylor, Prashant Bansode, Lonnie Wall, Rob Boucher Jr, Akshay Bogawat.


The purpose of the Application Architecture Guide is to improve your effectiveness building applications on the Microsoft platform. The primary audience is solution architects and developer leads. The guide provides design-level guidance for the architecture and design of applications. It focuses on the most common types of applications, partitioning application functionality into layers, components, and services, and walks through their key design characteristics.

We wrote this guide to help you with the following:

  • design more effective architectures
  • choose the right technologies
  • make more effective choices for key engineering decisions


Key Features

The guide includes the following:

  • Architecture Frame - is a map of some of the most important elements of architecture, including scenarios, quality attributes, application types, architecture styles and key engineering hot spots.
  • Application Types - a set of canonical application archetypes to illustrate common application types. Each archetype will be described in terms of the target scenarios, technologies, patterns and infrastructure it contains. Each archetype will be mapped to the canonical app frame. They are illustrative of common app types and not comprehensive or definitive.
  • Application Feature Frame - a common set of hot spots for key engineering decisions.
  • Quality Attributes - a set of qualities/abilities that shape your application architecture: performance, security, scalability, manageability, deployment, communication, etc.
  • Layered Application Reference Example - describes at a meta-level, the tiers and layers that an architect should consider. Each tier/layer will be described in terms of its focus, function, capabilities, common design patterns and technologies.
  • Principles, patterns and practices - using the frames as backdrops, the guide overlays relevant principles, patterns, and practices.

Chapters


Part I, Fundamentals

Part II, Design

Part III, Layers

Part IV, Archetypes

Appendix


Personal tools