The Apache Software Foundation unveiled recently your plans to phase out the use of mirrors supported by various organizations and volunteers.
This in favor of be able to organize the download of Apache project files by implementing a Content Delivery Network (CDN), which will eliminate problems like mirror desynchronization and delays due to content distribution through mirrors.
It should be remembered that in its beginnings the Apache Software Foundation did not have more than its own servers for the hosting and distribution of content, with which with the subsequent growth these servers were not enough for the demand exerted by the thousands of users around the planet.
For this reason, in order to share the load, the "mirror" system became popular.
It is not enough to create and release useful software. As an open source database, an important part of the Apache Software Foundation (ASF) job is to help get that software into the hands of users.
To do so, we have relied for many years on the contributions of individuals and organizations to provide a mirror infrastructure to distribute our software. We are now retiring that system in favor of a content delivery network (CDN) and we take a moment to thank all the individuals and organizations that helped bring ASF software into the hands of millions of users.
And it is that the Apache Software Foundation mentions that currently the use of mirrors is not justified by itself, since as such the volume of files placed on a mirror has grown from 10 to 180 GB in the last 20 years.
This also represents today in space and above all pollution that can be reduced using content delivery technologies which have advanced and the cost of traffic decreased.
The note does not reveal which CDN will be used, it is only mentioned that the choice will be made in favor of a network with professional support and a level of service that meets the needs of the Apache Software Foundation.
Today those 10GB have grown to over 180GB so that one mirror can carry all the ASF software. The industry has also changed. Technology has advanced, bandwidth costs have been reduced, and mirror systems are giving way to content delivery networks (CDNs).
After discussion and deliberation, the ASF infrastructure team has decided to move our download system to a CDN with professional support and a level of service appropriate to the foundation status in the world of technology.
Our new delivery system is part of a global CDN with economies of scale and fast, reliable downloads around the world. We expect ASF users to see faster deployment of the software, without any lag that would normally be seen with a mirror system while local mirrors are synchronized with the primary instance.
ASF projects will see no difference in your workflow, just faster delivery of open source artifacts to your users. Once again, we would like to thank all the contributors who have helped raise mirrors over the past 20 years. Without the mirror system to deliver our software, we would never have gotten this far.
In addition, it should be noted that under Apache auspices it is already developing its own platform to create geographically distributed content delivery networks Apache Traffic Control, which is used in the Cisco and Comcast content delivery networks.
A few days ago, the Apache Traffic Control 6.0 release was released, which added support for generating and renewing certificates using the ACME protocol, implemented the ability to set locks (CDN Locks), added support for update queues, and added a backend for extracting PostgreSQL keys.
Finally If you are interested in knowing more about it, you can check the details In the following link.