Application Architecture Guide

From Guidance Share

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

← Previous diff
Revision as of 22:20, 25 April 2009 (edit)
JD (Talk | contribs)

Next diff →
Line 9: Line 9:
* make more effective choices for key engineering decisions * make more effective choices for key engineering decisions
 +<br clear="all" />
== Key Features == == Key Features ==
The guide includes the following: The guide includes the following:
Line 16: Line 17:
* principles, Patterns, and Practices. * principles, Patterns, and Practices.
* technologies and capabilities. * technologies and capabilities.
-<br clear="all" />+ 
== Chapters == == Chapters ==

Revision as of 22:20, 25 April 2009

- 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
  • application feature frame
  • a set of canonical application types
  • principles, Patterns, and Practices.
  • technologies and capabilities.


Chapters

The following overview shows you how to execute the agile architecture method:

Personal tools