You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "liubao (Jira)" <ji...@apache.org> on 2020/02/21 03:03:00 UTC

[jira] [Closed] (SCB-21) service orchestration

     [ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

liubao closed SCB-21.
---------------------
    Resolution: Won't Fix

> service orchestration
> ---------------------
>
>                 Key: SCB-21
>                 URL: https://issues.apache.org/jira/browse/SCB-21
>             Project: Apache ServiceComb
>          Issue Type: New Feature
>          Components: Java-Chassis
>            Reporter: Eric Lee
>            Priority: Major
>              Labels: roadmap
>         Attachments: Proposal for integrating ServiceComb into Camel.pdf
>
>
> 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)