Database Reference
In-Depth Information
One could extend this list of framework, adding more fragmentation; however, from any
practical point of view, these ten frameworks (that is, 6 + 4) are pretty adequate for divid-
ing the entire technical infrastructure into distinguished and consistent areas of imple-
mentation principles, standards, and patterns. However, what are patterns, the main sub-
ject of this topic?
Through the examples we already explored, we can agree on some of the most frequent
problems that are well known to any practicing architect. These problems are common,
and so will the solutions be. Thus, commonly approved solutions for regular problems
have a common name pattern. The history of patterns in distributed computing is quite
similar to the history of the SOA itself. It was a stiff curve from love and passion to hate
and disbelief, and there is a very simple explanation for it; that is, the pattern is not a pan-
acea and not an ultimate purpose of your solution design. It would be prudent if from now
on you exclude the following questions from your architectural vocabulary:
• What kind of pattern will we apply here?
• Is this design according to the approved pattern catalog?
Search WWH ::




Custom Search