Skip to content

Commit a33582f

Browse files
authored
Merge pull request #10 from edly-io/danial/add-adr-for-transformers-architecture
Add ADR for transformer architecture
2 parents 8e60257 + 0c7a3ac commit a33582f

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
4. Transformers Architecture
2+
============================
3+
4+
Status
5+
------
6+
7+
Approved
8+
9+
Context
10+
-------
11+
12+
We can develop event transformers either using the “Backend” architecture
13+
or “Processor” architecture. Making the transformers “backends” will result
14+
in relatively more nesting in the configurations as this “backend” will have
15+
its own configurations.
16+
17+
If we decide to develop the event transformers as “processors”, it will result
18+
in less complexity in the code since the transformer can be easily appended in
19+
any backend’s (router or logger) processors’ pipeline.
20+
21+
22+
Decision
23+
--------
24+
25+
Transformers will be developed as event processors that can be added in
26+
any backend’s pipeline. Then the transformed events can be used for any purpose,
27+
either for simply logging using the LoggerBackend or to route events using
28+
EventRoutingBackend.
29+
30+
Consequences
31+
------------
32+
33+
Developing transformers as processors will result in relatively less complex
34+
configurations and it would provide us wider range of use cases for the transformers.

0 commit comments

Comments
 (0)