CDN and edge
How a request reaches your application, what the edge answers on its own, and what it hands to a Function.
Every request to a Gigadrive Network application arrives at the edge before your code sees it. The edge resolves the hostname to a deployment, then either answers from the CDN cache or object storage, or forwards the request to a Function.
Most traffic to a content-heavy site never becomes an invocation. These pages cover what that decision depends on, and how to change it.
How a hostname and path resolve to an asset, an object or a Function.
CachingWhich layer answers a request, and how long it holds the response.
Static assetsHow build output is uploaded, addressed and served without compute.
Image optimizationResize and re-encode images at request time, under a policy you set.