Custom budget CDN for Iconify API
This tutorial is a part of Iconify API hosting instructions.
What is CDN? CDN is short for content delivery network. It is set of servers spread out across the globe, that deliver content to visitor as fast as possible. AnyCast DNS connects visitors to the closest server.
This tutorial is intended to be used if you are setting up your custom Iconify API and want to take advantage of CDN.
This tutorial is intended for stateless CDN.
Stateless means every request does not have a state. That is, request does not depend on previous request, so if visitor is connected to different edge server than he visited before, it wouldn't make any difference.
Iconify API is stateless. It does not allow visitors to store anything, it does not track anything, it does not send any cookies. There is no central server and each API server is separate from other servers.
First, you need to create multiple origin servers in various parts of the world.
All servers need to be configured to serve exactly the same data for exactly the same host name. So you need to configure multiple identical servers. There are plenty of tools that can automate this process, however they are not part of this tutorial.
For tutorial on how to set up hosting for Iconify API, see hosting tutorial.
After setting up multiple servers, you want to direct users to the closest server.
Adding multiple "A" records to your domain won't achieve that. You need AnyCast DNS.
AnyCast DNS is expensive. Very expensive. What if you don't have thousands of dollars to spend? Good news is there is one alternative solution: Amazon's Route53 latency routing.
Route53 latency routing works by redirecting visitor to the closest Amazon datacenter.
What if you are not hosting your websites at Amazon datacenters? You can host at datacenters not far from Amazon (same country or state), which is more than good enough to redirect visitors to the closest of your servers.
- You need an AWS account. Sign up at AWS main page.
- Go to Route53 page (sign in if needed).
- Click "Hosted Zones" link, click on your domain or create a new zone.
Then you need to add records for each server you have in your CDN. Click "Create Record Set", enter subdomain name in "Name" field, enter IP address in "Value" field, in "Routing Policy" field select "Latency". That last part is very important: that makes it possible to redirect visitors to the closest server based on latency. Select region closest to your server's physical location, enter something in "Set ID" field.
If you are running script on AWS service, instead of entering IP select click "Yes" for "Alias" option and select AWS instance.
Click "Create" button to add that record.
Create several more records for your other servers. For each record enter the same subdomain, but different IP and different region.
By the time you are finished it should look like this:
Notice there are 3 records for "icons.simplesvg.com" pointing to different IP addresses with different region set up.
That's it. When visiting, user will be redirected to one of 3 IPs: 220.127.116.11, 18.104.22.168, 22.214.171.124 depending on which AWS datacenter is the closest. It is precise enough to create a budget custom CDN.