Application Patterns

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

Application Patterns provide fast before and after skeletal views of end to end application scenarios. They expose key engineering decisions where deployment and quality of service requirements shapes application design.

Last edited Feb 6, 2009 at 12:20 AM by prashantbansode, version 10

Comments

killbergjcp Jan 27, 2009 at 5:35 PM 
This is a good start on actual concrete, implemented application patterns. What might be helpful, given the large and cross-cutting amount of information in the Application Architecture Guide book, is calling out the Application Types (Archetypes) and Architecture Styles that are used to compose each Application Pattern. This may already be implied (Two-Tier equates to N-Tier Arch Style and Rich Client equates to Rich Client Application App Type) but a hard reference someplace in the pattern might make it more obvious. I like to think of the App Arch guide as the pieces that are referenced/composed to define the Application Patterns, and the Application Patterns are the real world, concrete patterns that a large audience can identify with and implement.