6

We are just researching a couple of API gateways, in particular Kong. Looking through their documentation it seems they support request/response transformation.

However, if I understand this correctly, this seems limited to headers.

Does Kong support API Aggregation like Netflix does it?

blekione
  • 10,152
  • 3
  • 20
  • 26
Phil
  • 73
  • 1
  • 3

1 Answers1

5

No, by default one http request into Kong will only match to one upstream url.

The Kong request and response transformation plugins handle simple Header, Body and Query String manipulation but Kong doesn't handle API aggregation.

Obviously, Kong is very easy to modify via it's own plugin mechanism but emulating what appears to be complex metadata driven dynamic orchestration tool that Netflix describe (via Lua) is going to be non-trivial.

If you used Kong here it would likely only be as the gateway (which it does well) and build out simple orchestration APIs yourself that aggregated your backend calls.

Mark Jones
  • 12,156
  • 2
  • 50
  • 62
  • 1
    Thank you for your comment, this was really helpful. Based on your information we are now looking into the [Backend-For-Frontend pattern](https://www.thoughtworks.com/insights/blog/bff-soundcloud) to provide said aggregation. – Phil Aug 15 '16 at 23:02
  • Nope, I have been evaluating Kong. This feature is missing. Write a plugin seems to be the answer for most missing features. – Dojo Sep 19 '19 at 05:54
  • 1
    Also, wondering if we have a solution now? – tiger_groove Jan 08 '21 at 20:15