viewing Apigee X documentation.
View Apigee Edge documentation.
An API proxy is a managed facade for backend services. A basic API proxy configuration consists of a ProxyEndpoint (defining the URL of the API proxy) and a TargetEndpoint (defining the URL of the backend service).
Using service callouts to invoke a backend service in an API proxy with no routes to a target endpoint is technically feasible, but results in the loss of analytics data about the performance of the external service.
An API proxy that does not contain target routes can be useful in cases where you do not need to forward the request message to the TargetEndpoint. Instead, the ProxyEndpoint performs all necessary processing. For example, the ProxyEndpoint could retrieve data from a lookup to the API service's key/value store and return the response without invoking a backend service.
You can define a null Route in an API proxy, as shown here:
A proxy using a null route is a "no target" proxy, because it does not invoke a target backend service.
It is technically possible to add a service callout to a no target proxy to invoke an external service, as shown in the example below:
<!-- /antipatterns/examples/service-callout-no-target-1.xml --> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ProxyEndpoint name="default"> <Description/> <FaultRules/> <PreFlow name="PreFlow"> <Request> <Step> <Name>ServiceCallout-InvokeBackend</Name> </Step> </Request> <Response/> </PreFlow> <PostFlow name="PostFlow"> <Request/> <Response/> </PostFlow> <Flows/> <HTTPProxyConnection> <BasePath>/no-target-proxy</BasePath> <Properties/> <VirtualHost>secure</VirtualHost> </HTTPProxyConnection> <RouteRule name="noroute"/> </ProxyEndpoint>
However, the proxy cannot provide analytics information about the external service behavior (such as processing time or error rates), making it difficult to assess the performance of the external service.
- Analytics information on the interaction with the external service ( error codes, response time, target performance, etc.) is unavailable
- Any specific logic required before or after invoking the service callout is included as part of the overall proxy logic, making it harder to understand and reuse.
If an API proxy interacts with only a single external service, the proxy should follow the basic design pattern, where the backend service is defined as the target endpoint of the API proxy. A proxy with no routing rules to a target endpoint should not invoke a backend service using the ServiceCallout policy.
The following proxy configuration implements the same behavior as the example above, but follows best practices:
<!-- /antipatterns/examples/service-callout-no-target-2.xml --> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ProxyEndpoint name="default"> <Description/> <FaultRules/> <PreFlow name="PreFlow"> <Request/> <Response/> </PreFlow> <PostFlow name="PostFlow"> <Request/> <Response/> </PostFlow> <Flows/> <HTTPProxyConnection> <BasePath>/simple-proxy-with-route-to-backend</BasePath> <Properties/> <VirtualHost>secure</VirtualHost> </HTTPProxyConnection> <RouteRule name="default"> <TargetEndpoint>default</TargetEndpoint> </RouteRule> </ProxyEndpoint>
Use Service callouts to support mashup scenarios, where you want to invoke external services before or after invoking the target endpoint. Service callouts are not meant to replace target endpoint invocation.