How Does Cloud CDN Work?
- Suppose we need the user to make a request to someone’s website therefore the request is routed to the nearest Google Edge node thereby making the flow of traffic easier and faster.
- From there the request is routed to the backend or the origin of the global HTTPS Load Balancer.
- The cloud CDN is enabled, the content is directly served to the cache which helps in managing the cacheable content that helps to serve the content faster in the future.
- Cloud CDN caches this content on its own when we use the recommended “cache mode” to cache all static content. If more control is needed, one can direct Cloud CDN by setting HTTP headers on the responses.
- On receiving a request by Cloud CDN it looks for the cached content using a cache key. This is typically the URI, but it can customize the cache key to remove protocols, etc.
- Cloud CDN attempts to get the content from a closed cache. If the nearby cache has content, it sends it to the first cache by using cache-to-cache fill. Otherwise, the request is sent to the origin server.
- The maximum lifetime of the object in a cache is defined by the TTLs set by the cache directives for each HTTP response or cache mode.
How to Integrate Cloud CDN To Your Project?
The cloud refers to the telecommuting servers on the internet that manages and handles all big data and applications. It is internet-based computing where shared resources and information are given to computers on demand like a public utility. Cloud is surrounded by different models like IaaS, PaaS, and SaaS. Cloud CDN is a much broader concept of cloud computing.