Icon

Merging multiple internal APIs at the edge streamlines data delivery, reduces latency, and improves user experience by providing a unified API response. This approach also reduces the load on origin servers and enhances application performance.

Loading...

https://www.edgecompute.live/api-orch

Copied to clipboard!

Demonstrates how EdgeWorkers can be used to merge multiple internal APIs into a single API response from a user experience perspective.

Icon landscape
Dynamic Flexibilty

Modify in-flight content on its way between client and origin server and back to clients.

Icon landscape
Ease Development

Enable developers to modify application behavior without touching origin server logic.

Related Examples

View More
Icon Card background
Cachekey Device Type

This example includes the device type (tablet or mobile) from a PMUSER variable in the computed cache key for an Edge Server.

View Case
Icon Card background
Device Routing

Implements modification of the forward origin path of the URL to return device-specific content.

View Case
Icon Card background
Dynamic Callback

Demonstrates how an EdgeWorker can wrap a JSON response with a dynamic unique callback function leveraging Response Provider and Stream API for efficient content transformation. The EdgeWorker should be enabled on JSON requests containing a callback query parameter, which can be managed via Property Manager. When such a request comes in, this EdgeWorker removes the callback query parameter, makes a sub-request to fetch the JSON data, and serves it as a stream. The EdgeWorker code adds a prefix with the callback function name captured from the query parameter and a suffix. Both JSON data and transformed data can be cached using standard ““Caching”” behavior in Property Manager if caching is allowed.

View Case