By Bhushan Nikhar
Here's a practical Apigee guide. I am writing this guide for someone who is freshly trying to learn Apigee.
Nowadays, almost all product companies expose their APIs to facilitate interactions for consumers. However, exposing APIs introduces multiple challenges:
Apigee is an API gateway for your organization. It intercepts each request from an API consumer to your APIs, enabling powerful transformations, monitoring, security, and management.
Apigee sets up an API proxy for each API. This proxy acts as the interface between your consumers and your backend API.
An API product can contain one or more API proxies. It allows you to group APIs and manage access collectively.
Policies define transformations, validations, or access rules for requests and responses. You can attach policies at various stages in the request-response flow.
Each API proxy has two endpoints:
Requests traverse multiple stages (pre-flow, flow, post-flow) in both proxy and target endpoints. Each stage can have policies applied for security, transformation, or logging.
Each API has an API proxy. API proxies are grouped into API products. Access control is applied at the API product level to restrict or allow specific consumers.
Apigee provides a UI to inspect eachhop's execution time and the transformations or mediations applied.
Typical structure of an API proxy:
apiproxy ├─ apiproxy/Policies ├─ apiproxy/ProxyEndpoint/default.xml ├─ apiproxy/TargetEndpoint/default.xml └─ apiproxy/Resources/*.jsx