IDG Contributor Network: Designing a content delivery strategy
Technologies like content delivery networks, cloud compute and storage, container schedulers, load balancers, web application firewalls, DDoS mitigation services and many more make up the building blocks that serve the online applications of organizations today. But the entry point to every one of those applications is an often-ignored bit of infrastructure: DNS. As the internet has mushroomed in size and traffic, DNS has adapted to become a critical factor in application delivery. Organizations that rely on content delivery networks (CDNs) can work with their DNS provider(s) to create a CDN strategy that best serves them and their customers.CDN: the what and the why A CDN’s job is what it sounds like: deliver content such as images, video, html files and javascript from a network of distributed systems to end-users. CDNs have been around for about as long as Managed DNS companies. Akamai is usually considered the first serious CDN player, and the company rose to prominence during the first dot-com boom. Generally, CDNs deliver content over HTTP or HTTPS, the web protocols, although there are occasionally use cases like video delivery where other protocols come into play.To read this article in full or to leave a comment, please Continue reading

The data center software also integrates with Kubernetes.
The new book should be out around the 29th of December, give or take a few days. For readers interested in what Ethan and I (and Ryan, and Pete Welcher, and Jordan Martin, and Nick Russo, and… the entire list is in the front matter), the general idea is essentially grounded in RFC1925, rule 11. There is really only a moderately sized set of problems computer system needs to solve in order to carry data from one application to another. For instance, in order to transport data across a network, you need to somehow format the data so everyone can agree on how to write and read it, ensure the data is carried without errors, ensure neither the sender nor the receiver overrun or underrun one another, and find some way to allow multiple applications (hosts, etc.), to talk over the same media. These four problems have somewhat proper names, of course: marshaling, which involves dictionaries and grammars; error control; flow control; and multiplexing. So the first step in understanding network engineering is to figure out what the problems are, and how to break them apart.
The company’s virtualization effort is Project Ocean.