Chris Pirillo’s CDN in a Box looks to make Web sites hum at ‘Google-like speeds’

Seattle super geek Chris Pirillo has a loyal following who love his offbeat musings on technology. But sometimes Pirillo’s network of sites, including LockerGnome.com, get overloaded with traffic. Faced with that challenge, Pirillo and his team have developed a new service called CDN in a Box that’s designed to handle huge traffic spikes and accelerate page loads to “Google-like speeds.”

Chris Pirillo’s CDN in a Box looks to make Web sites hum at ‘Google-like speeds’
geekwire.com

Interesting point - but how is it different than CloudFlare?

Not to rain no anyone's parade here, but real CDN providers like Akamai, Cotendo and EdgeCast offer a far superior service for far less money.

This thing is hosted on GAE, which is not fast, and doesn't have the global footprint of even the smallest CDN player.

GAE is fast for things Akamai isn't. GAE actually has a more global foot print, because it has more peering agreements than any provider on the planet, and while you would be right if this was a CDN for pushing 1 Gig files, it is a CDN for pushing your 60k images all over the place. The cost of a Cache Miss on Akamai for a small file is VERY high, and nearly non-existent on GAE.

Building the right tool on the right platform for the right kind of job. (oh and pricing, You can't even get started with Akamai for less than $1000 a month, which goes a long ways on that pricing thing. Plus Akamai's 8-12 cents is not really 12 cents when you pay for storage, and all of the other nickel and dime things. CDN In A Box is just Simple Pricing, and Simple Deployment. ( you ever tried to write a blog post then upload the images to Akamai?)

CloudFlare doesn't block legit crawlers either. It does cache responses to crawlers so if a page hasn't changed and Google crawls it again the request doesn't burden the origin.

What's interesting about CDN in a Box is they're serving off a single IP. The problem with this strategy is Google classifies sites for crawl purposes by IP. That means if one site on CDN in a Box falters, all the other sites on CDN in a Box will suffer (e.g., Google turning down crawl velocity or completely removing them from the index). The same problem occurs if there's anything spammy or compromised by malware.

At CloudFlare, we tried the CDN in a Box strategy when we launched more that a year ago. We quickly found it had serious negative impacts on site rankings. We spent considerable time working directly with Google and the other search engine crawl teams on a solution. Today, sites on CloudFlare actually get the highest crawl velocity setting because of this work, which we've seen positively impact site rankings.

I'm curious to hear more about CDN in a Box's plans, discussions with search engine crawler teams, and technologies they've developed to overcome this challenge.