[
https://issues.apache.org/jira/browse/SC-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Lee updated SC-21:
-----------------------
Attachment: Proposal for integrating ServiceComb into Camel.pdf
proposal for integrating ServiceComb into Camel. Before that, we need to
refactor the service registry module to provide a more friendly client for
camel to use.
> service orchestration
> ---------------------
>
> Key: SC-21
> URL: https://issues.apache.org/jira/browse/SC-21
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
> Reporter: Eric Lee
> 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
(v6.4.14#64029)
