Talk:Content delivery network

message: What about some information on the typical basis of payment?
For example, many content distribution or delivery services have a monthly platform fee.
Often, a certain amount of transit (e.g. 200 GB or 1.5 TB, etc.) is included with the platform fee.
Then, there is usually a tiered per GB transit rate for data over and above that included in the platform fee.
Some providers call the platform fee a minimum commitment, but it is effectively the same.
Also, a one time set up fee is common.
Thoughts?  — Preceding unsigned comment added by 206.47.249.247 (talk) 00:52, 9 January 2014 (UTC)
replies: text: While this is an older comment from 2014, I do agree that a section in this CDN article about "Business models" could be a useful contribution and would help people understand more about how CDNs work. I think the challenge could be to find reliable sources that would provide an overview of CDN business models and practices. There might be a journal article or paper that someone has published on this topic. And maybe a media site has written something about CDN business practices. (My concern is that I could also see 'advertorial'-style paid articles being out there that are biased toward one type of CDN or another.) Regardless, if appropriate sources could be found, I could see this being a useful contribution. - Dyork (talk) 01:21, 8 May 2020 (UTC)
thread_title:  Payment basis and typical costs 

message: Both Google (Google Hosted Libraries) and Microsoft (Microsoft Ajax Content Delivery Network) have CDNs that serve a high volume of script content. I couldn't find articles on the Wiki to point to either one, but their omission from this article seems to be an oversight worth looking into. -Draeth Darkstar (talk) 13:58, 19 February 2015 (UTC)
replies: text: Five years later I note that no one has added these two CDNs to the list. It would need some further research, but if these two CDNs are still appropriate, it may make sense to add them. This might, though, require creating a new Script CDNs sub-section under the section Notable content delivery service providers given that these are different from other CDN types. We would also want to research whether there are other similar CDNs providing similar services that should be listed. (For example, I would wonder if one of the zillion Amazon AWS services would do this.) - Dyork (talk) 01:27, 8 May 2020 (UTC)
thread_title:  Notable Script CDNs 

message: Recently I was in a discussion where we were talking about when CDNs first started being used within the Internet's infrastructure. Someone said they started 20 years ago while someone else thought it was newer. My first reaction was to go to this Wikipedia page... where I discovered that there is not a History section. What do others think about adding such a History section? Looking at the history of the page and this Talk page, it looks like perhaps we'd need to watch that section for some CDNs trying to edit the text to promote their company. BUT, I think it could be a useful addition. When I get some time, I would be willing to start such a section, but if someone else has cycles to get it going, that would be great. - Dyork (talk) 14:38, 22 April 2020 (UTC)
thread_title:  Add section on history of CDNs? 

message: In 2017 Addy Osmany of Google started referring to software solutions that could integrate naturally with the Responsive Web Design paradigm (with particular reference to the <picture> element) as Image CDNs.. The expression referred to the ability for a web architecture to serve multiple versions of the same image through HTTP, depending on the properties of the browser requesting it, as determined by either the browser or the server-side logic. The purpose of Image CDNs was, in Google's vision, to serve high-quality images (or, better, images perceived as high-quality by the human eye) while preserving download speed, thus contributing to a great User experience (UX).
Arguably, the Image CDN term was originally a misnomer, as neither Cloudinary nor Imgix (the examples quoted by Google in the 2017 guide by Addy Osmany) were, at the time, a CDN in the classical sense of the term. Shortly afterwards, though, several companies offered solutions that allowed developers to serve different versions of their graphical assets according to several strategies. Many of these solutions were built on top of traditional CDNs, such as Akamai, CloudFront, Fastly, Verizon Digital Media Services and Cloudflare. At the same time, other solutions that already provided an image multi-serving service joined the Image CDN definition by either offering CDN functionality natively (ImageEngine) or integrating with one of the existing CDNs (Cloudinary/Akamai, Imgix/Fastly).
While providing a universally agreed-on definition of what an Image CDN is may not be possible, generally speaking, an Image CDN supports the following three components :
* A Content Delivery Network (CDN) for fast serving of images.
* Image manipulation and optimization, either on-the-fly though URL directives, in batch mode (through manual upload of images) or fully-automatic (or a combination of these).
* Device Detection (aka Device Intelligence), i.e. the ability to determine the properties of the requesting browser and/or device through analysis of the User-Agent string, HTTP Accept headers, Client-Hints or JavaScript.
The following table summarizes the current situation with the main software CDNs in this space:
 Main Image CDNs on the market
Name               	CDN           	Image Optimization   	Device Detection
Akamai ImageManager	Y             	Batch mode           	based on HTTP Accept header
Cloudflare Polish  	Y             	fully-automatic      	based on HTTP Accept header
Cloudinary         	Through Akamai	Batch, URL directives	Accept header, Client-Hints
Fastly IO          	Y             	URL directives       	based on HTTP Accept header
ImageEngine        	Y             	fully-automatic      	WURFL, Client-Hints, Accept header
Imgix              	Through Fastly	fully-automatic      	Accept header / Client-Hints
PageCDN            	Y             	URL directives       	based on HTTP Accept header
Passani (talk) 17:24, 13 May 2020 (UTC)
thread_title:  Image Optimization and Delivery (Image CDNs) 

message: Created first archive page, Talk:Content_delivery_network/Archive_1, following H:ARC process. Moved old, completed sections of this page from 2009-2013 over to that archive page. You can browse the page or you can search using the box on top of this page - Dyork (talk) 01:14, 8 May 2020 (UTC)
thread_title:  Create Archive 1 page 

message: Just flagging that today, in this revision, there was the addition of links and text related to imagekit.io by an editor with only a single contribution so far. This might be a legitimate edit, or it might be someone from that company directly editing the page. I don't know enough about Imagekit to know if the edit is appropriate. Flagging it so that other editors with greater knowledge of image CDNs can take a look. - Dyork (talk) 01:03, 16 June 2020 (UTC)
thread_title:  Question about addition of imagekit.io 

message: I gave up during the first paragraph
"distributing the service spatially relative"
"CDNs are a layer in the internet ecosystem."
Meaningless. 
And it gets worse "A more recently defined and robust solution is provided by the Open Pluggable Edge Services"
And I came here via the Cloudflare page. I am no clearer about why Cloudflare is blocking some sites recently. Neither it seems are the sites/browsers being blocked
Cannonmc (talk) 02:53, 7 May 2022 (UTC)
thread_title:  Any chance someone could write this in proper English