官术网_书友最值得收藏!

API aggregation

Aggregation at the gates. This applies to mobile or third-party use cases that do not want to know the details of the aggregation and instead would want to expect one data structure over a single request. The API gateways are designed to do this aggregation and then expose a unified service to the client. The API gateways can also select to eliminate any data sections in the aggregate service if it is not required to be shown during content aggregation:

Benefits

The benefits of using the API aggregation pattern are as follows:

  • The individual service details are abstracted from the client by the API gateway. Hence it gives the flexibility to change the services internally without affecting the client tier.
  • Better in bandwidth constrained scenarios where running parallel HTTP requests may not be a good idea.
  • Better in UI processing constrained scenarios where processing power might not be enough for concurrent page generation.

Trade-offs

The trade-offs associated with the API aggregation pattern are as follows:

  • Where there is sufficient bandwidth, the latency of this option is higher than the aggregation by the client. This is because the API gateway waits for all the content to be aggregated before sending the data out to the client.
主站蜘蛛池模板: 溆浦县| 仙桃市| 施甸县| 塘沽区| 元阳县| 栾川县| 巴楚县| 河源市| 广东省| 泰州市| 台北市| 汝城县| 阳谷县| 金昌市| 讷河市| 大理市| 汽车| 台山市| 山阴县| 津市市| 类乌齐县| 田阳县| 广宗县| 罗源县| 德安县| 通山县| 汝阳县| 博爱县| 广东省| 沂源县| 汕尾市| 桓台县| 桦川县| 宁乡县| 丹阳市| 吉林省| 舞钢市| 江山市| 通州区| 米脂县| 济宁市|