-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Data Composition / Aggregation #883
Comments
We do not support this natively in Express Gateway. Next time use Stackoverflow or Gitter :) |
@XVincentX - I did use Gitter 😂 |
I know — but keep in mind I’m not 24/7 on the Gitter channel and creating issues for questions just drags out my personal time; I understand your needs — but I hope you understand mine.
|
Sorry @XVincentX - It was not meant to bother you - I understand your personal time :D |
I'll try to look into this myself - maybe I can come up with an alternative policy for the proxy which allows data composition |
Quick question - does Express Gateway support something called Result Aggregation or Data composition?
So for example, client makes call to gateway
GET /user/{id}
Gateway calls three microservices and combines their responses as follows:
GET http://microservice1.com/accounts/{id}
->RETURNS { "id":"1", "email":"john@doe.com" }
GET http://microservice2.com/memberships/for/{id}
->RETURNS [ { *MEMBERSHIP* }, { *MEMBERSHIP* } ]
GET http://microservice3.com/avatars
->RETURNS { "avatar": "http://example.com/avatar/1" }
Gateway returns ->
(a) Is above possible? (b) Or should I really create my own policy for this to make this work?
(c) Or is this considered bad practice?
The text was updated successfully, but these errors were encountered: