I’ll introduce the content of a CDN implementation proposal I made for a certain web service.
Overview: What is a CDN?
What exactly is a CDN?
CDN stands for Content Delivery Network, and simply put, it's a collection of servers that handle data distribution on behalf of your own server. As you can tell from the word "Network" being used, it's not distribution from a single location but from multiple locations, which is characterized by considering not only redundancy within locations but also redundancy at the location level. In essence, this means that even if an entire data center suffers from a disaster like fire, the same data can be distributed from a different data center.
CDN Advantages/Disadvantages
Advantages
- Can reduce CPU and bandwidth usage on application servers
- Improves page loading speed even when accessed from overseas
- Benefits from an SEO perspective
Disadvantages
- Operators need to consider that image files and other content are cached
- Costs money
CDN Services
CloudFront if Sticking with AWS Products
Fastly with Fast Cache Purging
CDN Summary
That’s all from the Gemba where I recommend implementing a CDN.