Live data from Hacker News

Rolling your own CDN for $25 in 1 hour

scalescale.com

71–80 of 93 posts

Re: Rolling your own CDN for $25 in 1 hour

#71

I would highly recommend Varnish using S3 as a backend origin. Add to that a few 100TB.com dedicated server and you have an extremely cheap CDN with pretty decent bandwidth and minimal maintenance. CDNs have the advantage that they control more of the stack so can do more precise routing and have more edge nodes in more places. However, under the right circumstances, you can take the above quite far before a real CDN…

100TB.com specifically forbids using their service to create a CDN in their ToS[0]. 9. Acceptable Use/Illegal Activity d. We strive to maintain a high level of service, and a lot of customers depend on our high standards of quality. As such, we will not provide Services to those that are using our Services for: vii Using the Services for a content delivery network or content distribution network (CDN). An authorized…

people forget the story of simplecdn

Re: Rolling your own CDN for $25 in 1 hour

#72
post #69
post #7

Earlier quoted context omitted.

Actually, with DigitalOcean, you get quite a lot of bandwidth for the price. Additionally, their transfer limits are high (1TB for the $5 instances), and overage is only $0.02/GB. If you combine this with something like Route 53's anycast latency-routed DNS, it can work very well.

with DigitalOcean they ask you do not run a CDN: https://www.digitalocean.com/community/questions/do-you-have...

I'm assuming that's a paid CDN with clients like CloudFlare or Akamai, not you distributing your website to multiple datacenters in order to serve more clients faster. If you happen to use CDN like DNS features to route the client to the closest Digital Ocean datacenter, you're probably in the clear.

Re: Rolling your own CDN for $25 in 1 hour

#73
post #69
post #7

Earlier quoted context omitted.

Actually, with DigitalOcean, you get quite a lot of bandwidth for the price. Additionally, their transfer limits are high (1TB for the $5 instances), and overage is only $0.02/GB. If you combine this with something like Route 53's anycast latency-routed DNS, it can work very well.

with DigitalOcean they ask you do not run a CDN: https://www.digitalocean.com/community/questions/do-you-have...

That question is 2 years old, and refers to an "unlimited bandwidth" fair-use policy. DO does not have unmetered bandwidth, so is it still relevant?

Their current policy FAQ says they do not even explicitly forbid Tor exit nodes, although there is a stern warning, so why would they disallow a proxy configuration dedicated solely to your site?

Re: Rolling your own CDN for $25 in 1 hour

#74
post #72
post #69

Earlier quoted context omitted.

with DigitalOcean they ask you do not run a CDN: https://www.digitalocean.com/community/questions/do-you-have...

I'm assuming that's a paid CDN with clients like CloudFlare or Akamai, not you distributing your website to multiple datacenters in order to serve more clients faster. If you happen to use CDN like DNS features to route the client to the closest Digital Ocean datacenter, you're probably in the clear.

Good point. I wonder if they meant "we ask you don't run a CDN _service_" rather than just a CDN for your website.

Afterall, what is the difference between serving assets out of your webserver

Re: Rolling your own CDN for $25 in 1 hour

#75
post #27

Nice. For tutorials like this it would be nice to see more details on the "how" of each step. For example: "We setup DNS info to point here (both NS1 and NS2..." That's great, but it would be nice to see: "Using the geodns web-based configuration tool, we setup DNS info to point here (both NS1 and NS2..." or "Running on , we setup DNS info to point here (both NS1 and NS2..." or "By editing /etc/ on the , we setup DNS…

I think Genius and DigitalOcean = a match made in heaven. The quality would go from "the best" to "untouchable", if the comments were value adding. Imagine being able to dive deeper into any piece of the tutorial you wanted.

not to sound like a n00b, but what is Genius in your context?

Re: Rolling your own CDN for $25 in 1 hour

#76

I would highly recommend Varnish using S3 as a backend origin. Add to that a few 100TB.com dedicated server and you have an extremely cheap CDN with pretty decent bandwidth and minimal maintenance. CDNs have the advantage that they control more of the stack so can do more precise routing and have more edge nodes in more places. However, under the right circumstances, you can take the above quite far before a real CDN…

100TB.com specifically forbids using their service to create a CDN in their ToS[0]. 9. Acceptable Use/Illegal Activity d. We strive to maintain a high level of service, and a lot of customers depend on our high standards of quality. As such, we will not provide Services to those that are using our Services for: vii Using the Services for a content delivery network or content distribution network (CDN). An authorized…

There's a fundamental difference between reselling CDN services, and running a caching web proxy as part of your own infrastructure for your own use.

Re: Rolling your own CDN for $25 in 1 hour

#77
post #75

Earlier quoted context omitted.

I think Genius and DigitalOcean = a match made in heaven. The quality would go from "the best" to "untouchable", if the comments were value adding. Imagine being able to dive deeper into any piece of the tutorial you wanted.

not to sound like a n00b, but what is Genius in your context?

I think he means Genius the company (formerly RapGenius) which annotates the web. (http://genius.com/)

Re: Rolling your own CDN for $25 in 1 hour

#78
post #75

Earlier quoted context omitted.

not to sound like a n00b, but what is Genius in your context?

I think he means Genius the company (formerly RapGenius) which annotates the web. ( http://genius.com/ )

oh ok thanks, I thought that, but I was also thinking maybe it was some tech stack like a docker container for a moment.

Re: Rolling your own CDN for $25 in 1 hour

#79
post #11

I'm more than a little bit concerned that the article doesn't point out the serious risk of running a single DNS server for the records. I get that they're trying to keep things simple for their demo, but unsuspecting folks following this guide are in for quite a shock when their GeoDNS is taken out by a single physical server fault.

added this to the article in the "Todo" section. thanks for the feedback.

In similar efforts, I also really enjoyed the slides from talk at DNS OARC 2014 about Anycast on a shoe string:

http://www.slideshare.net/natmorris/anycast-on-a-shoe-string

Post reply on HN