Live data from Hacker News

An Uber-like CDN

medium.com

71–80 of 86 posts

Re: An Uber-like CDN

#71
It seems a little odd to use GitHub as the CDN for your JavaScript library. Like what if this got really popular, what’s to stop GutHub for shutting it down for abusing their hosting? If I were a customer for a CDN, I would feel more comfortable if they owned their own domain and could control how (and if!) their JavaScript is available to customers.

Anyways, other than that it’s a fun concept. I like the P2P nature of it.

Re: An Uber-like CDN

#72
post #16

Earlier quoted context omitted.

>Something doesn't add up here. They're actively telling third parties to lease cloud servers with large amounts of free bandwidth: Bare-metal servers are much better is our case. Please note, bandwidth is not free. You can follow the links and see the actual price for it. If LeaseWeb tells you: 1 Gbps dedicated/unlimited per $143/month, it means you can use it 24x7. >- They are paying the third party less than what…

> If LeaseWeb tells you: 1 Gbps dedicated/unlimited per $143/month, it means you can use it 24x7. While that is true in theory, if you in practice saturate your bandwidth 24x7 by reselling it your contract will probably get cancelled (or at least that is the case for most "unlimited" contracts). I don't think you actually answered the questions of the parent.

That's possible true for the Yes 0.0005$ per GB egress and a provider in Europe still makes money.

Re: An Uber-like CDN

#73
This isn’t good for SEO, which is highly dependent on speed. The CDN data is loaded via JavaScript, meaning crawlers might not load it. I don’t know what this is trying to solve, CloudFlare pretty much already fixes the egress charges problem.

Re: An Uber-like CDN

#74
post #16

Earlier quoted context omitted.

>Something doesn't add up here. They're actively telling third parties to lease cloud servers with large amounts of free bandwidth: Bare-metal servers are much better is our case. Please note, bandwidth is not free. You can follow the links and see the actual price for it. If LeaseWeb tells you: 1 Gbps dedicated/unlimited per $143/month, it means you can use it 24x7. >- They are paying the third party less than what…

> If LeaseWeb tells you: 1 Gbps dedicated/unlimited per $143/month, it means you can use it 24x7. While that is true in theory, if you in practice saturate your bandwidth 24x7 by reselling it your contract will probably get cancelled (or at least that is the case for most "unlimited" contracts). I don't think you actually answered the questions of the parent.

There is a difference in this case between 'unlimited' and 'unmetered'. The limit is on the throughput (1Gbps) rather than the total bandwidth which is itself naturally limited by the throughput x time.

That being said I could still see this being against TOS if you end up chewing up SSDs, hosting dodgy content or running at full power constantly.

Re: An Uber-like CDN

#75
post #16

Earlier quoted context omitted.

>Something doesn't add up here. They're actively telling third parties to lease cloud servers with large amounts of free bandwidth: Bare-metal servers are much better is our case. Please note, bandwidth is not free. You can follow the links and see the actual price for it. If LeaseWeb tells you: 1 Gbps dedicated/unlimited per $143/month, it means you can use it 24x7. >- They are paying the third party less than what…

> That's why the _Peer_ sets the price for his service. But that breaks the economics of this, no? If you're in the US and charge $6/TB and I'm in Germany and charge $100/TB, why would traffic ever go to my server? If your US server gets overloaded, am I now making $100/TB? How does the network ensure that this is both fair and competitive? Moreover, how can a customer know that they're not going to get a surprise bi…

A customer can switch on/off regions. Also, they can set up a cap for every region. You can do it with regular CDNs as well, it's just a setting.

Re: An Uber-like CDN

#76
post #67
post #18

Earlier quoted context omitted.

>1. Performance. also please note: if you have 1 image on the page - we have to do 2 requests (1 metadata, 1 download) if you have 50 images on the page - we have to do 51 requests only (1 metadata for all images, 50 downloads)

> if you have 50 images on the page - we have to do 51 requests only (1 metadata for all images, How do you know the nearest peer has all the images at hand?

to answer this question, I will write another article how we distribute cache among the Peers. Long story short:

- we divide web cache in buckets

- these buckets have different sizes

- we know a list of files in every bucket

- we know what buckets every Peer has

Re: An Uber-like CDN

#77
post #27

Earlier quoted context omitted.

>a CDN isn't just about bandwidth, it is about _disk_ The disk performance - is the weakest part of the Peer. It is a part you can't guarantee any QoS on a cheap server. The idea is to keep popular cache on Peers in memory. Everything else we will host from a limited number of regular servers (belong to Farba), with high-performance disk subsystem. >Cache management (eviction, invalidation, etc) is done where? yes. Y…

> The disk performance - is the weakest part of the Peer. It is a part you can't guarantee any QoS on a cheap server. The idea is to keep popular cache on Peers in memory. Everything else we will host from a limited number of regular servers (belong to Farba), with high-performance disk subsystem. I use a CDN to serve about 50GB of files stored on my origin, which turn over every week or so (a new 50GB every week). W…

for unpopular content, we will deploy a limited number of servers (belong to Farba) with a performant disk subsystem. A web cache storage is a separate option in every CDN: if you want your files always in "hot" cache, you have to pay extra.

Re: An Uber-like CDN

#78

What stops a peer from, say, injecting malicious JavaScript into pages? Or going rogue and serving porn for every request for a JPEG? What if they only do it for every 1000th request? You could send a hash of the file to the client from the coordination server and check it. If the hash isn't valid, you can re-request the file from another peer. But I don't think you can trust the client to report abuse: a malicious c…

>Or, the site owner could manipulate the coordination JavaScript to report the downloaded file as invalid/corrupt/tampered with, and then just not re-request the file (and there's nothing you can do to stop them). So in that case, the site owner is managing to not pay for the service (assuming you don't bill for downloads that were reported as invalid).

This fraud is possible. We collect logs from three sources:

- the Balancer (belong to Farba)

- the Peer

- the User

We can analyze every single case of suspicious behavior.

Re: An Uber-like CDN

#79
as a web user, no thanks, I do not trust your peers or really you even. I trust cloudflare because they have earned that trust over decades.

as a web developer, no thanks, I do not want to trust my app’s speed to your profit incentive or margin.

Re: An Uber-like CDN

#80
post #54

This says it's a system for delivering content "efficiently", but it doesn't look like this manages that. Normally loading a resource is a round trip to your server, which might be a bit inefficient because your server could be on the other side of the world. But what they replace it with is: 1. Round trip to Farba to get metadata. 2. Round trip to your "driver" to get the resource. 3. Computing the hash of the resou…

everything works in our sandbox. We need a couple of customers to collect real data. I'll definitely going to post again with these numbers.
Post reply on HN