Remember the book ” Application Architecture for .NET – Designing Applications and Services “of the patterns & practices, 2002?
Although old, this book is read by many people in the market, providing the basis for several application scenarios that are still operating, firm and strong.
Part of the success is due to layering the book adopts the .NET solutions, when we saw the Business Entity, Business Workflow, Business Components, the interface of dedicated hosting services, among others.
If you became curious, see the diagram below:
Recalled right? Why am I remembering this kind of design? See, it’s been eight years since its publication, even today, we have an organization of components often based on the architecture above. Even at that time, another important design positions the layers of consumption and exports of services, as shown below:
See, people talked about a standard interface via Web services protocols to SOAP / HTTP / WS-I, allowing the import and export data to external application services.
If it already existed 8 years ago, what has changed in the architecture do today? To think about it, see drawing below, I removed the Application Architecture Guide 2.0:
The figure illustrates a service architecture, where we see basically the same layers of 8 years ago.
Interesting or not?
The conclusion is that good architecture patterns are permanent, lasting enough and taste a good investment project. Thus, when designing your solution, try to surround some scenarios with good architectural patterns. Certainly, applying good choices, you’re guaranteed a long life for your solution. But look, an anti-pattern is also being excessive in the use of PATTERN. Use them sparingly, always!