Application Architecture for .NET: Designing Applications and Services

This guide is for you if you are an architect or developer lead or need to:

• Determine how an application will be split into components,
• Choose what technologies will be used in a transactional line of business application or service,
• Design what management and security policies should be applied, and
• Decide how the application will be deployed.

This guide applies to transactional or OLTP applications that follow a layered design and can be distributed across many physical tiers by using the following technologies: ASP.NET, Web Services, Enterprise Services (COM+), Remoting, ADO.NET, and SQL Server. Some design principles presented in this guide may be useful on other similar scenarios.

What Is in This Guide?
Chapter 1: Introduction
This first chapter presents the overall goal of distributed application design, presents how services and service integration relates to traditional application development, and presents a simple retail scenario that is used as a theme for examples in the guide.

Chapter 2: Designing the Components of an Application or Service
This chapter walks you through a distributed application, starting at the user interface, and identifies different types of components or layers commonly used in successful applications. It describes the major technology or design decisions that must be made and the guiding principles for the design of these components.

Chapter 3: Security, Operational Management, and Communications Policies
In this chapter, you learn how different aspects–such as authorization and exception management–affect the design of the application layers, and how design decisions in these areas can permeate through your application. This chapter also discusses the choice of communication mechanisms.

Chapter 4: Physical Deployment and Operational Requirements
This chapter explains how the logical component layers presented above should be deployed in an infrastructure built of many physical tiers and shows common successful deployment patterns that arise when combining the logical component layers, physical tiers, and operational requirements.

Chapter 5: Appendices
The appendices include a glossary, a map of Microsoft products and technologies that allow you to implement or enhance the application component layers discussed in Chapter 2 and a list of related patterns and names applied in the industry to these layers.

Read More/Download

Microsoft Application Architecture Guide

This guide is primarily written for developers and solution architects who are looking for guidance on architecting and designing applications on the Microsoft platform and the .NET Framework. However, this guide will benefit any technologist who is generally interested in the field of application architecture and design, wishes to understand the underlying patterns and principles behind good application design on the .Microsoft platform or the .NET Framework, or is new to the Microsoft platform or the .NET Framework.

The goal of this guide is to help developers and solution architects build effective, high quality applications on the Microsoft platform and the .NET Framework more quickly and with less risk by leveraging tried and trusted architecture and design principles and patterns.

The guide provides an overview of the underlying principles and patterns that provide a solid foundation for good application architecture and design. On top of this foundation, the guide provides generally applicable guidance for partitioning an application’s functionality into layers, components, and services. It goes on to provide guidance on identifying and addressing the key design characteristics of the solution and the key quality attributes (such as performance, security, and scalability) and crosscutting concerns (such as caching and logging). The guide builds still further and provides guidance that is more specific on the architecture and design of the most common application types, such as Web, rich Internet applications (RIA), rich client, services, and mobile applications.

The guidance is presented in parts that correspond to major architecture and design focus points. It is designed to be used as a reference resource, or it can be read from beginning to end.

The guide will help you to:

• Understand the underlying architecture and design principles and patterns for developing successful solutions on the Microsoft platform.
• Identify appropriate strategies and design patterns that will help you design your solution’s layers, components, and services.
• Identify and address the key engineering decision points for your solution.
• Identify and address the key quality attributes and crosscutting concerns for your solution.
• Choose the right technologies for your solution.
• Create a candidate baseline architecture for your solution.
• Identify patterns & practices solution assets and further guidance that will help you to implement your solution.

Note that while the guide is extensive, it is should not be considered a complete and comprehensive treatise on the field of application architecture and design. The guide is intended to serve as a practical and convenient overview of and reference to the general principles of architecture and design on the Microsoft platform and the .NET Framework.

Read More/Download