Enterprise Solution Patterns(TEST!!!)

This is a collection of patterns that will help you use Microsoft .NET, which contains
many objects that follow patterns we’ve found useful. These objects are brought to
life by the common language runtime which makes for strongly-patterned objects.
An easy way to think about this is that the runtime takes care of so many aspects
of an object that just the pattern parts are left. Patterns were important before the
common language runtime, but now they are even more important.
You will find here a collection of patterns that you will see in most every transactionprocessing
Web application. These sorts of applications are really important to
enterprise developers who are important to this book’s authors. This is an important
focus in the here and now. Of all the pattern books that could have been written about
.NET, this is the most likely to be important to you today. Thank you, authors.
I could go on about Web applications but I wanted to point out an even more
interesting thing about this collection. Whenever we pull patterns together our
choices say something important about how we work. Our philosophy of work
runs through our selections. For example, in the Design Patterns book, [Gamma, et. al,
Addison-Wesley], the philosophy was to make programs flexible. This is important,
of course, and some of those patterns are included here. But there are two other
philosophies present in this volume worth mentioning.
One philosophy is that in a continuously evolving environment like the enterprise,
every complexity has a cost. You’ll find a variety of patterns here that at first seem
contradictory. That’s because the authors know that successful enterprise applications
start simple and grow over time. Something simple works for a while then it needs
to be replaced. You’ll find patterns here for both the simple and its replacement.
This isn’t the same as doing it wrong and then making it right. Both patterns are
right, just not at the same time on a given project.
Another philosophy that runs through these patterns is that different people in the
enterprise use different patterns for different purposes. Some patterns are more
about the user experience than anything else. We can say that these patterns, and
the people that apply them, are working in service of the user. The more these folks
understand their users, the better they will be able to apply these patterns and the
better their programs will be for their effort. Contrast this to classic concerns of the
enterprise: efficiency, security, reliability, and so on. This collection includes patterns
about these problems, too. When you apply them you will be working in service
of the enterprise. It is also likely that you personally won’t apply all the patterns in
this book. That doesn’t mean that you can’t read them and understand more about
how at least some of your colleagues think.