Content Aggregation via Apigee - Bring in Google Hosted API Content
Apigee Edge enables you to quickly expose backend services as APIs. By creating an API proxy you provide a facade for the backend service that you exposed. The API proxy decouples your backend service implementation from the API that developers consume. These shields developers from future changes to your backend services. As you update backend services, developers are insulated from those changes and can continue to call the API uninterrupted.
In this lab you learn how to leverage Apigee to aggregate an existing API call with the content coming from google hosted database. You add recommendations to a products API; the recommendations come from data stored in the firestore database. The pattern, however, can be applied to a variety of use cases. Consider, for example, an endpoint that receives feedback on a product or service such as POST /v1/products/1234/feedback - using the Natural Language API you can enrich the payload with sentiment scoring.
Similarly, you could readily inject image URLs into a weather endpoint by calling the Search API and aggregating results from the Weather Underground API.
What you'll do
Create and configure a Firestore Extension
Updated an API proxy in Apigee Edge
Test your API
加入 Qwiklabs 即可阅读本实验的剩余内容…以及更多精彩内容！
- 获取对“Google Cloud Console”的临时访问权限。
- 200 多项实验，从入门级实验到高级实验，应有尽有。
Upload data to Firestore
Create a service account and key
Create and test the Products API proxy in Apigee Edge