Menu
Consider a dynamic content html web site with lots of static .js and image baggage must be hosted in a single location. The site will soon have a few 1000 new users clustered in a single country on the other side of the world. This new remote country has a Amazon S3 node and all users in that country will be within 1000Km of the S3 node.
To improve the user expperience in the remote country I propose to locate the largest and most referenced static files on a local server close to that remote user community and rewrite URLs when servicing those users.
My feeling is that using a commercial CDN would be overkill in this situation and directly referencing our own manually managed S3 static content would give us more control particularly for occasional urgent patches to JavaScript.
580
Build your own CDN setup takes place in four steps: CDNs can be built using cloud instances or physical machines. Best ISP(s) and routing principles should be implemented for an optimal solution. You also need to configure Origin server(s) and PoP(s) (Point of Presence)
A content delivery network, or content distribution network (CDN), is a geographically distributed network of proxy servers and their data centers. The goal is to provide high availability and performance by distributing the service spatially relative to end users.
Keep in mind that a CDN is necessary if your company fits in with only one of the points. You should seriously consider a CDN if: Your site is growing at an exponential rate – A regular server is going to have a tough time handling a spike in traffic, unless you prepare for it with a CDN.
If you are already using Amazon S3 to store your static content, it makes sense to use Amazon's CloudFront CDN.
You can start using it and get all the benefits of the CDN without too much effort.
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
