CDN
“The ideal method” is to store the metadata about the image and then copy the image to a CDN for serving that to a user. This way your site isn't impacted by all of the requests needed to get those images, resulting in a more performant site.
Using CloudFront as CDN can match with default strategy for startups of using AWS products and AWS credits for startups.
Replacing paths of images
Instead of S3 URLs, we can add a subdomain, like images.websitename.com or cdn.websitename.com.
I think it might be a great improvement for SEO. But probably you can get DMCA complaints. But it's just an additional thing to solve.
- What is a CDN? How does a CDN Work? | Imperva
- Content Delivery Networks — What is a CDN?
- Cloud CDN: Content Delivery Network | Google Cloud
- https://docs.microsoft.com/en-us/azure/cdn/cdn-overview
- 4 ways startups say a modern CDN supports their goals | Fastly
- What Startups Should Know Before Choosing a CDN
- Amazon CloudFront for Media
- Improve your website performance with Amazon CloudFront | Networking & Content Delivery.
- Bulk Loading from Amazon S3 — Snowflake Documentation
- How to Deliver Content Faster – Amazon Web Services (AWS)
- AWS CloudFront: Everything You Need to Know
- Amazon CloudFront (AWS's CDN)
- How to Use AWS CloudFront: Deploying Amazon's CDN and Using It at a Discount - Reblaze Blog
Saving Millions of Images Series
Top comments (0)