You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Architecture and patterns for Data Integration. Working on collaboratively maintaining architecture patterns.
3
3
4
-
Working on collaboratively maintaining architecture patterns.
4
+
The pattern structure (Design and Solution Pattern layout) always is as follows:
5
+
6
+
* <title>, the name of the patterns
7
+
* Purpose, a short statement what the pattern is trying to achieve or explain. What is the intent?
8
+
* Motivation, a short overview of the background and relevance of the pattern. Why is there a need?
9
+
* Applicability, a listing of where this pattern can be expected to play a role.
10
+
* Structure, the main section with the pattern details.
11
+
* Implementation Guidelines, any references to how to implement this pattern (Design Patterns only). Note that the Solution Pattern is intended to explain the specifics in a technical context. This is meant to capture any generic topics.
12
+
* Considerations and consequences, meant to offer some alternative views and experiences as to what it means to take a certain decision.
13
+
* Related Patterns, any references towards futher reading and related content.
14
+
15
+
the <title> is in Header 1 format, the sections are in Header 2 format.
0 commit comments