> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/e/edge-computing.md). # Edge Computing Edge computing is a distributed computing model that processes data closer to where it is generated or consumed, rather than relying on a centralized data center. By moving computation to the "edge" of the network -- near end users or IoT devices -- edge computing reduces latency, decreases bandwidth usage, and enables real-time processing. Edge computing environments range from small IoT gateways to globally distributed CDN edge nodes. Cloud providers offer edge compute services such as Cloudflare Workers, AWS Lambda\@Edge, and Deno Deploy, which run application code at points of presence around the world. Edge computing is directly relevant to API gateway architecture. An edge-deployed API gateway processes requests at the nearest edge location to the client, handling authentication, rate limiting, request routing, and response caching without a round trip to a central server. This approach significantly reduces API response times, especially for geographically distributed users, and provides inherent resilience against regional outages. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/glossary/e/edge-computing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.