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

Experience-based APIs

Experience-based APIs represent a different approach to resource-based APIs. Here, the concept is One-Size-Fits-All (OSFA). Basically, the key to experience-based APIs is providing endpoints that are focused on the experience itself, which isn't only the user's experience—it could be the home screen experience.

The following example shows the dashboard-screen operation being directly connected to the Nintendo resource, thus expressing the experience of the screen on Nintendo:

/nintendo/dashboard-screen

This concept came from Netflix and, in general, it is an extension of the proxy pattern, where new proxy endpoints will be designed, developed, and configured to focus on the business requirements of the API consumers.

The following diagram shows how the Experience-based APIs building blocks connect to the external world (web, mobile, and so on) and with downstream systems such as the Legacy API:

主站蜘蛛池模板: 谢通门县| 金湖县| 山西省| 贡嘎县| 夏河县| 松阳县| 张家川| 山阴县| 江陵县| 上饶县| 东至县| 慈溪市| 舒城县| 平阴县| 乳山市| 平凉市| 和田市| 金阳县| 抚松县| 东兴市| 繁昌县| 蓬莱市| 葫芦岛市| 浮山县| 柘城县| 墨脱县| 镇雄县| 定结县| 平乡县| 册亨县| 台前县| 章丘市| 郑州市| 崇信县| 云安县| 巴中市| 康马县| 会东县| 台湾省| 松江区| 怀柔区|