Introduction

Published: March 31, 2005

This blueprint discusses design considerations and related issues for implementing the Microsoft .NET Framework in an enterprise-class organization.

The Application Infrastructure Architecture Blueprint introduced application architecture options, including concepts and technologies such as .NET and COM component models, Microsoft Message Queuing (also known as MSMQ), and the role of Internet Information Services (IIS). That blueprint also discussed ten different design options for implementing the logical layers of an application across different physical tiers and trust zones, including architectural advantages and disadvantages of each design option.

On This Page
Who Should Read This BlueprintWho Should Read This Blueprint
Knowledge PrerequisitesKnowledge Prerequisites
Business NeedBusiness Need
ReferencesReferences

Who Should Read This Blueprint

This blueprint is written for enterprise architects who are responsible for designing application infrastructure and also for IT personnel responsible for configuring or deploying applications created using the .NET Framework. The information provided in this blueprint relates directly to the guidance in the Application Infrastructure Architecture Blueprint.

Knowledge Prerequisites

The reader of this blueprint should have an understanding of the different application architecture designs described in the Application Infrastructure Architecture Blueprint.

The “Security” section in this blueprint describes administrable security features of the .NET Framework. However, administering security requires a good understanding of the .NET Framework security model, a full description of which is outside the scope of this blueprint.

Business Need

The role of information technology (IT) in the enterprise continues to change at an accelerating pace, shifting the focus from cutting costs to helping drive revenue and profits. This change in focus requires an emphasis on quick, cost-effective integration with suppliers, partners, and customers outside the corporate local area network (LAN) and the firewall. In short, it means doing more with less. In the present environment, organizations are not only trying to react more quickly to rapid changes in the market place, they are also trying to reduce costs and simplify the complexities of their IT infrastructures.

The .NET Framework is the portion of the application infrastructure that provides a manageable environment for running applications. The key advantages of the .NET Framework include the following:

Provides IT professionals with the ability to integrate existing systems with its native support for Web services.

Assists with the deployment of software for both users and Web servers.

Facilitates the development of software with improved security, scalability, manageability, performance, and reliability.

Helps developers be more productive by:

Making it easier for them to reuse existing code.

Enabling them to integrate components written in any of the supported programming languages. (Currently, more than 20 languages are supported.)

Helping them build software more easily for a wide range of devices using same skills and tools.

References

Further information about design and deployment of .NET framework may be found at the following URLs:

To familiarize yourself with the fundamentals of the .NET Framework see the following URL:

msdn.microsoft.com/library/en-us/cpguide/html/cpconinsidenetframework.asp

For a good introduction to the .NET framework see the following book:

Title: Introducing Microsoft .NET

Author: David S. Platt

Publisher: Microsoft Press; 3rd edition (May 2003)

ISBN: 0735619182

For an excellent reference guide on the use of the security features available in Microsoft's .NET framework, see the following book:

Title: .NET Framework Security

Authors: Brian A. LaMacchia, Sebastian Lange, Matthew Lyons, Rudi Martin, Kevin T. Price.

Publisher: Addison-Wesley Pub Co; 1st edition (April 24, 2002)

ISBN: 067232184X


**
**