If you're deploying an application on AWS, it's likely that you'll use CDN frequently. I've noticed this service being used quite frequently these days, and recently I took advantage of its caching feature, so I wanted to make a note of it.
Currently, I'm working on a project to create an image hosting service using Ruby on Rails. When a user requests an image with a URL, our server responds with an edited blob image. However, processing images requires a lot of CPU usage, and this task can be overwhelming for a server to handle every time.
That's where CloudFront comes in. CloudFront is an AWS-provided CDN. Caching involves temporarily storing frequently accessed content, such as images, in edge locations. When a user requests content, the CDN routes the request to the nearest edge location and serves the content from its cache.

If you're deploying an application on AWS, it's likely that you'll use CDN frequently. I've noticed this service being used quite frequently these days, and recently I took advantage of its caching feature, so I wanted to make a note of it.

Currently, I'm working on a project to create an image hosting service using Ruby on Rails. When a user requests an image with a URL, our server responds with an edited blob image. However, processing images requires a lot of CPU usage, and this task can be overwhelming for a server to handle every time.

That's where CloudFront comes in. CloudFront is an AWS-provided CDN. Caching involves temporarily storing frequently accessed content, such as images, in edge locations. When a user requests content, the CDN routes the request to the nearest edge location and serves the content from its cache.

CloudFront cash should be used for Images and videos