Chapter 10. Enterprise Application Modeling

Part I of this book presented the .NET technologies that you need to create distributed applications. Each one of these technologies is a key to solving a particular problem or unlocking a particular feature for a distributed system. However, you can't apply these technologies blindly. If you do, the result will be a disorganized, poorly performing tangle of code. Your use of features such as XML Web services, .NET Remoting, threading, and COM+ services must emerge from a well-planned design.

This chapter considers the fundamental considerations for planning a distributed system. These include the role each component should play, how different parts of the system should communicate, and where business rules should take effect. We'll also tackle the question of state, a few key design patterns (factories, facades, and interfaces), and some guidelines to follow when choosing among different .NET technologies.