Application Architecture Guide 2.0 BETA 1 - Willy .Net

your application, and can provide additional services such as basic mapping between the
format of the data exposed by the service and the format your application requires.
Approach for Application Architecture
The approach to architectural design can be divided into the following steps:
1. Choose your application type. The application type you are designing will have a major
impact on all of the other decisions you make. Deployment considerations for a Web
application are different to those for a mobile application. Authentication techniques are
different for a service and a rich client. Start by understanding your application type, and
how that choice impacts your overall architecture.
2. Choose your deployment topology. How you will deploy your application will shape your
overall design. Will you be deploying a Web application on multiple tiers Will you be
deploying a RIA implementation over the Internet Understand your logical and physical
deployment in order to better understand your constraints and architectural requirements.
3. Choose your architectural styles. The type of application you are designing, together with
architectural goals and constraints, determine which architectural styles are a best fit. Will
your design be based on SOA principles Will you use an Enterprise Service Bus Are you
building an S+S or Peer-to-Peer application The architectural styles described in this guide
provide a set of principles that will make architectural decisions more cohesive and
directed.
4. Choose appropriate technologies. Choose technologies based on capabilities and patterns
suited to your scenario.
5. Determine how to address quality attributes. Consider how your design will address the
common problems associated with each quality attribute. How will you design for
availability, security, maintainability and reusability Use the quality attributes guide to
create a robust design that will stand the test of time.
6. Determine how to address cross-cutting concerns. Walk the architecture frame and
understand how each cross-cutting concern impacts your design. Consider architectural
requirements for tasks such as caching, communication, data access, layering, and
validation.
This approach will allow you to design a candidate architecture that can be reviewed, tested,
and compared to your requirements and constraints. Do not get lost in the details; focus on the
big steps and build a framework that you can use to develop the rest of your architecture and
design.
Application Types
Your choice of application type will be related both to the technology constraints and the type
of user experience you plan to deliver. Use scenarios to help you choose an application type.
For example, if you want to support rich media and graphics delivered over the Internet, then a
Rich Internet Application (RIA) is probably the best choice. However, if you want to support
28