Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
Description
orchestration of service invocation and aggregation of data from multiple services based on configured rule
eg. a user request requires calling service a/b/c/d in order: request -> a -> b -> c -> d -> response
this creates a tight coupling among services a/b/c/d.
better solutions:
request -> aggregator -> response (aggregator calls a/b/c/d in sequence based on configured rule)
request -> a -> message queue -> b -> queue -> c -> queue -> d
both ways no coupling among the services.
this epic is about solution 1
Attachments
Attachments
1.
|
integration with service center |
|
Closed | Unassigned |
2.
|
integration with zipkin |
|
Closed | Unassigned |
3.
|
integration with highway transport |
|
Closed | Unassigned |
4.
|
serial service invocations |
|
Closed | Unassigned |
5.
|
parallel service invocations |
|
Closed | Unassigned |
6.
|
fallback invocation on exception |
|
Closed | Unassigned |