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