Whether we have a streaming service and need to cache videos/images/w.e., or if we have a search engine and want to cache the results instead of hitting the ALB across the world to recompute every time, we can cache the dynamic responses from the ALB as well. What is cached depends on the rules you setup.
Next time someone loads the page from that region, CF does not go all the way back to that bucket in us-east-1, but their local edge cache. After the first request in a region (let's continue the Japan example), the static assets are cached on CF's Japan server(s). Their experience on our site could probably be better.ĬF allows us to cache those S3 files "at the edge". Let's say we have a bunch of images in a S3 bucket in us-east-1 (remember that S3 is a global service, but the objects are stored in one region unless replication is turned on). I like to think of CF as a cache next to the user's location. form submissions), and CF to put the two together and return the response. We can use S3 for static, ALB for dynamic (i.e. Like you mentioned, serving up static assets is one of them. There are a couple of use cases for CF in front of ALB. Origins can be S3 buckets, but also ALBs, custom IPs, etc ( ) Hi there, That's right! CF has this concept of "origins", basically almost like routing rules for figuring out which resource provides which part of the response.
0 kommentar(er)
