Building Your Own CDN for Fun and Profit
pasztor.at
Building Your Own CDN for Fun and Profit
1–10 of 65 posts
Re: Building Your Own CDN for Fun and Profit
#2We currently use KeyCDN which works out well, both performance & money wise. You may want to try it out.
Re: Building Your Own CDN for Fun and Profit
#3I have tried using AWS Route53's latency based records, but for some reason, it always didn't work for me. I need to check it again.
Re: Building Your Own CDN for Fun and Profit
#4> Second, BGP routes are not that stable. While DNS requests only require a single packet to be sent in both directions, HTTP (web) requests require establishing a connection to download the content. If the route changes, the HTTP connection is broken.
I thought Cloudflare uses Anycast to avoid targeted DDOS? How do they handle changing routes during HTTP requests?
Re: Building Your Own CDN for Fun and Profit
#5I am curious, if anyone knows how well does Akamai work in the CDN world?
Re: Building Your Own CDN for Fun and Profit
#6> Second, BGP routes are not that stable. While DNS requests only require a single packet to be sent in both directions, HTTP (web) requests require establishing a connection to download the content. If the route changes, the HTTP connection is broken. I thought Cloudflare uses Anycast to avoid targeted DDOS? How do they handle changing routes during HTTP requests?
Anycast means there are multiple routes going to the same destination. You get the route that is the shortest path via BGP to the anycast IP (least number of BGP hops). Once you have an established TCP session via one route, it will remain established through that route, as long as that route is still the “shortest” between your IP and the anycast IP.
The route will not “change” unless cloudflare changes their routing, or you change your location/IP so that a shorter route exists. Once you’ve changed your IP, you’ve already interrupted any TCP sessions anyway.
You might find these two blog posts from LinkedIn to be helpful:
https://engineering.linkedin.com/network-performance/tcp-ove...
https://engineering.linkedin.com/blog/2016/04/the-joy-of-any...
Re: Building Your Own CDN for Fun and Profit
#7I don't understand how his use of Traefik gets round the SSL pain point?
> Using SSL/TLS certificates
> The next pain point is using SSL/TLS certificates. Actually, let’s call them what they are: x509 certificates. Each of your edge locations needs to have a valid certificate for your domain. The simple solution, of course, is to use LetsEncrypt to generate a different certificate for each, but you have to be careful. LE has a rate limit, which I ran into on one of my edge nodes. In fact, I had to take the London node down for the time being until the weekly limit expires.
> However, I am using Traefik as my proxy of choice, which supports using a distributed key-value store or even Apache Zookeeper as the backend for synchronization. While this requires a bit more engineering, it is probably a lot more stable in the long run.
Re: Building Your Own CDN for Fun and Profit
#8if you have a specialized application knowing how to do this can be quite useful. CDN pops are almost not existent across much of the Middle East and Africa. Sometimes building your own is the only way until a commercial offering becomes available.
Re: Building Your Own CDN for Fun and Profit
#9I am curious, if anyone knows how well does Akamai work in the CDN world?
Terrible to work with and not all that performant as well. Also they caused us a 24+ downtime by a forced configuration change from their side, which undid some configurations their professional services implemented (yeah, some parts of the UI is only modifiable by PS). Luckily we had Cloudfront integration as backup, so switched over to that until finally Akamai team decided fix our problem.
Re: Building Your Own CDN for Fun and Profit
#10Author mentions why not use Cloudflare that CDN cache is purged often. If you want to verify if it happens for your content. You can try this tool - http://cloudperf.speedchecker.xyz/cloudflare-tester.html
Side effect of this tool as you might have guessed is that using it will actually prolong the time your content stays in their cache.