More Related Content Similar to .NET Architecture for Enterprises (20) More from Wade Wegner (8) .NET Architecture for Enterprises1. .NET Architecture
for Enterprises
Wade Wegner
Architect, Microsoft Corporation
wade.wegner@microsoft.com
http://www.architectingwith.net/
6. Window Server
Tibco
Apache
Web Services
Python
SQL Server HTML
.NET
SOA
JavaScript BizTalk
AS/400 Oracle
IIS
13. Did he now need to care
about different things?
64. Principles
To view all orders placed by a customer, the
user indicates the customer ID. The program
displays an error message if the customer does
not exist. If the customer exists, the program
displays name, address, date of birth, and all
outstanding orders. For each order, the
program gets ID, date, and all order items.
Find Pertinent Objects First
66. Principles
Program to an interface, not an
implementation
Favor Low Coupling
72. Advanced Principles
public class Foo
{
IDoSomething _doSomething = null;
public Foo(IDoSomething doSomething)
{
_doSomething = doSomething;
}
}
Dependency Inversion Principle
194. Summary
Testability & Security
198. Summary
The Presentation Layer
208. wade.wegner@microsoft.com
http://architectingwith.net
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.