Blog Archives
Launch of Cotendo, a new CDN / ADN
Cotendo, a new CDN backed by VC heavyweights Sequoia Capital and Benchmark Capital, has launched. The technical founders are ex-Commtouch; the VPs of Ops and Marketing are ex-Limelight. Cotendo is positioning itself as a software company (rather than an infrastructure company, per the market shift I blogged about a few months ago), but it’s not a software pure-play — it’s got the usual megaPOP-model deployment. However, they’re positioning themselves more as a fourth-generation approach.
Three things make this launch notable — an ADN service similar to Akamai’s (thus breaking the monopoly Akamai has had since the Netli acquisition), a global load-balancing solution beefed up into an arbitrage service (for multiple delivery resources), and real-time analytics. Plus, all of us CDN-watchers can experience a wry sense of relief to see that Cotendo, unlike practically every other CDN to launch in the last two years, is not focused on video.
Again, I apologize for what is essentially a news blurb, but since I expect it’s going to be a significant subject of client inquiry, I shouldn’t be giving away analysis on my blog. Gartner’s Invest clients are going to ask what this means in the e-commerce/enterprise space, and our mid-market IT buyer clients will want to know what it means for their options. Like usual, I’m happy to take inquiry. Also, more information about this will be going out in a research note.
Fourth-generation CDNs and the launch of Conviva
First-generation CDNs use a highly distributed edge model, and include companies like Akamai and Sandpiper Networks (whose acquisiton chain goes Digital Island, Exodus, Savvis, Level 3).
Second-generation CDNs basically try to achieve most of the performance of a first-generation CDN without needing hundreds of POPs, aiming for just a few dozen locations. Speedera (eventually acquired by Akamai) is the best example of a CDN of this type.
Third-generation CDNs follow a megaPOP model — two or three dozen huge points of presence, which they hope will be highly peered. Limelight, VitalStream (acquired by Internap), and the new entrants of the past two years are pretty much all megaPOP CDNs.
Fourth-generation CDNs are very different. They are a shift towards a more software-oriented model, and thus, these companies own limited (or even no) delivery assets themselves. Some of these are not (and will not be) so much CDNs themselves, as platforms that reside in the CDN ecosystem, or CDN enablers. Velocix (for their Metro product) and MediaMelon both reside in the fourth-generation space.
That gets us to the morning’s interesting announcement.
Conviva has come out of stealth mode with a powerhouse customer announcement — NBC Universal. Conviva is not a CDN in the traditional sense, but they’re part of the ecosystem for Internet video. Rather than owning delivery assets themselves, they’ve got a pure-play SaaS solution — a platform that can arbitrage resources from multiple content sources (multiple CDNs, data centers, etc.), as well as offer value-added services like real-time analytics and integration capabilities across those multiple sources. (From an ecosystem perspective, the closest analogue is probably Move Networks.)
What makes Conviva immediately notable is their ability to do real-time monitoring of the performance of every individual delivery, and seamlessly switch sources midway through playing a video, driven by metrics and business rules, thus allowing the customer to deliver consistently good-enough performance (i.e., a target of no buffering or other degradation) at the lowest price point, i.e., cost-arbitraged QoS.
I’ve been writing about the customer desire for control and the rise of the fourth-generation software “CDN” since last year. Conviva takes full advantage of the overlay model. I’d rate the significance of this launch on par with that of Netli’s (back in 2003), although obviously in a very different way.
Because it’s a particularly important launch, I know it’s going to be of substantial interest to Gartner’s Invest clients, and likely of significant interest to our media and telecommunications industry clients. As such, I’m refraining from blogging a detailed description or analysis of the company’s technology and strategy, its likely impact to the rest of the video delivery ecosystem (which goes beyond the CDNs themselves), and the more general impact of the conceptual shift that’s taking place with fourth-generation CDNs. If you have inquiry access, please feel free to use it. A note to clients will be published soon.
(Disclaimer: I was pre-briefed on this, and I am quoted in Conviva’s press release. As I almost always do, I wrote my own quote, rather than letting words be put in my mouth. As with all Gartner quotes in press releases, it is a statement about the market, and no endorsement of the vendor is implied.)
TCO tool for cloud computing
Gartner clients might be interested in my just-published piece of research, which is a TCO toolkit for comparing the cost of internal and cloud infrastructure.
A not-new link, but which I nonetheless want to draw people’s attention to as much as possible: Yahoo’s best practices for speeding up your web site is a superb list of clearly-articulated tips for improving your site performance and the user’s perception of performance (which goes beyond just site performance). Recommended reading for everyone from the serious Web developer to the guy just throwing some HTML up for his personal pages.
On the similarly not-new but still-interesting front, Voxel’s open-source mod_cdn module for Apache is a cool little bit of code that makes it easy to CDN-ify your site — install the module and it’ll automatically transform your links to static content. For those of you who are dealing with CDNs that don’t provide CNAME support (like the Rackspace/Limelight combo), are using Apache for your origin front-end, and who don’t want to fool with mod_rewrite, this might be an interesting alternative.
CDNetworks buys Panther Express
For many months now, CDN industry insiders have gossiped that Panther Express was in financial trouble. Panther was caught with the bad luck of mistiming the funding cycle, leaving them to try to raise capital at a point when the capital markets were essentially frozen. Moreover, a large percentage of their revenues were tied to no-commit or limited-commit contracts, and with CDN prices in free-fall for much of 2008, Panther was doubly screwed from the perspective of the money guys. As time wore on, the likelihood of an acquisition by either a rival CDN or a carrier wanting to get into the space became more and more likely — but the longer the potential acquirers could wait to pull the trigger, the more cheaply they could buy the accompany, especially since rumors of Panther’s financial difficulties were starting to scare off potential customers.
Enter CDNetworks, a global CDN based in South Korea, who in the last year has been aggressively trying to penetrate the North American market. CDNetworks acquired Panther Express yesterday, in a deal structured so that it merged its US and European-based operations with Panther. Panther’s CEO Steve Liddell (who has experience working with Asian-based companies through his past experience as president of Level 3’s Asia business) will lead the new entity.
Dan Rayburn has offered some numbers and claims the acquisition values Panther at about $5 million — which would be about one-quarter of its 2008 trailing revenues, and would leave me wondering how that compares to the book value of Panther’s deployed eqiupment.
I’ll simply say that, although I agree with Dan that this acquisition basically has zero impact on other players or on pricing in the market, I have a very different perspective on the acquisition itself, and carrier opinion of this space, and of the general market opportunity (especially in the context that CDN is much more than video), than Dan does. Gartner clients who want to talk about it, you’re welcome to schedule an inquiry with me.
(Sorry. I started to write a long and detailed analysis, and then realized that I was crossing the line on what Gartner views as acceptable analyst blogging, and what is full-fledged analysis that ought to be reserved for paying clients.)
Application delivery network adoption
A long-standing puzzle for myself and my various colleagues who cover application-fluent networking: Why don’t more SaaS providers adopt application delivery networks (ADNs), either via a service, or via application delivery controller (ADC) hardware?
Even if a SaaS vendor perceives their performance as being just fine for the typical US-based user, performance is often an issue in Europe, and frequently deteriorates sharply in Asia, especially China, and is erratic everywhere else depending on the quality of the country’s connectivity. (Change the names of the regions if the data center isn’t in North America.) Deploying an ADN helps to bolster performance for these users. And if it’s not cost-effective to do that for all users, why not charge extra for an accelerated service? (Yes, we understand that there are issues like “if we offer an accelerated service, are we implying our regular service is slow?” but really, that’s just a marketing issue. Performance can be a competitive differentiator and it’s also a revenue opportunity.)
Two interesting recent examples:
- Fog Creek’s CoPilot gets Akamai IP Application Accelerator service
- F5 does a China solution for its DevCentral portal
Yes, times are tough right now, so a SaaS company does have to evaluate the ROI carefully, but any SaaS provider with performance issues owes it to themselves to give this stuff a look. (And SaaS customers who have performance issues ought to be poking at their providers.)
Who is Distribution Cloud?
Matthew Sacks has blogged Keynote performance test results for Akamai via Distribution Cloud.
There are other Akamai resellers out there, but Distribution Cloud posts its prices publicly, starting at 50 GB for $150 per month ($3/GB), and going up to 1 TB for $2,200/month ($2.20/GB), with storage at $15/GB. That’s 10x the cost of Limelight with a Rackspace Cloud Files origin ($0.22/GB, no commit) — definitely not a commodity price, so it’s really the low commit that makes this interesting.
But the blog post got me wondering: Who is Distribution Cloud, anyway? Their website lists a phone number and the fact they’re in Cambridge, MA, but no address or anything else that indicates who the company is. A search on the phone number turns up that it’s registered to a David Reisfeld at 94 Rice St, phone service courtesy of Level 3. LinkedIn and Naymz have listings for a person who seems to match: a senior director, product management, CDN streaming services, at Level 3 — formerly a senior product manager at Akamai.
But that only deepens the mystery. Did Reisfeld run a reseller (since 2002, the site claims) while employed at Akamai, with the blessing of his employer? Is he fronting for a buddy? Is he still doing it while employed at a competitor, or is the name for the phone listing not current? If it’s not his company, whose is it?
Volume pricing for Amazon’s CloudFront
New volume pricing for Amazon’s CloudFront CDN takes effect today, February 1st. For US and Europe “edge” delivery, the price goes as low as $0.05/GB at the 1000+ TB level. For Hong Kong, it’s $0.09/GB at that level. For Japan, $0.095/GB. The pricing isn’t quite comparable to a traditional CDN because of the origin bandwidth fees and the per-request fee, but it’s still a useful benchmark.
For those who are mentally comparing this to the cost of bandwidth, those per-GB costs translate into $16/Mbps for US/Europe, and $29/Mbps for Asia. In a day and age when Cogent is splashing “Home of the $4 Megabit” across its home page, it might look like there’s still quite a bit of delta between bandwidth pricing and CDN pricing, but especially once you get out of the US, bandwidth costs escalate pretty dramatically beyond Cogent’s low-water-mark.
Nonetheless, Amazon’s volume pricing play ought to put to an end anyone’s hope that the elimination of some of the financially weaker CDN players is going to do anything significant to alleviate pricing pressure where it’s most severe — the entirely commoditized portion of the market. In fact, this explicit, transparent pricing is probably going to provide a nice bargaining chip. Even if a major media conglomerate isn’t going to use Amazon to deliver their video, it won’t stop its purchasing people from using these published prices to hammer CDNs during negotiations.
Akamai article in ACM Queue
My colleague Nick Gall pointed out an article in the ACM Queue that I’d missed: Improving Performance on the Internet, by Akamai’s chief scientist, Tom Leighton.
There is certainly some amount of marketing spin in that article, but it is nonetheless a very good read. If you are looking for a primer on why there are CDNs, or are interested in understanding how the application delivery network service works, this is a great article. Even if you’re not interested in CDNs, the section called “Highly Distributed Network Design” has a superb set of principles for fault-tolerant distributed systems, which I’ll quote here:
- Ensure significant redundancy in all systems to facilitate failover.
- Use software logic to provide message reliability.
- Use distributed control for coordination.
- Fail cleanly and restart.
- Phase software releases.
- Notice and proactively quarantine faults.
One niggle: The article says, “The top 30 networks combined deliver only 50 percent of end-user traffic, and it drops off quickly from there, with a very-long-tail distribution over the Internet’s 13,000 networks.” That statement needs a very important piece of context: the fact that most of those networks do not belong to network operators (i.e., carriers, cable companies, etc.). Many of them are simply “autonomous systems” (in Internet parlance) owned by enterprises, or which belong to Web hosters, and so forth. That’s why the top 30 account for so much of the traffic, and that percentage would be sharply increased if you allocated them the enterprises who buy transit from them. (Those interested in looking at data to do a deeper dive should check out the Routing Report site.)
News round-up
A handful of quick news-ish takes:
Amazon has released the beta of its EC2 management console. This brings point-and-click friendliness to Amazon’s cloud infrastructure service. A quick glance through the interface makes it clear that effort was made to make it easy to use, beginning with big colorful buttons. My expectation is that a lot of the users who might otherwise have gone to RightScale et.al. to get the easy-to-use GUI will now just stick with Amazon’s own console. Most of those users would have just been using that free service, but there’s probably a percentage that would otherwise have been upsold who will stick with what Amazon has.
Verizon is courting CDN customers with the “Partner Port Program”. It sounds like this is a “buy transit from us over a direct peer” service — essentially becoming explicit about settlement-based content peering with content owners and CDNs. I imagine Verizon is seeing plenty of content dumped onto its network by low-cost transit providers like Level 3 and Cogent; by publicly offering lower prices and encouraging content providers to seek paid peering with it, it can grab some revenue and improve performance for its broadband users.
Scott Cleland blogged about the “open Internet” panel at CES. To sum up, he seems to think that the conversation is now being dominated by the commercially-minded proponents. That would certainly seem to be in line with Verizon’s move, which essentially implies that they’re resigning themselves to the current peering ecosystem and are going to compete directly for traffic rather than whining that the system is unfair (always disengenuous, given ILEC and MSO complicity in creating the current circumstances of that ecosystem).
I view arrangements that are reasonable from a financial and engineering standpoint, that do not seek to discriminate based on the nature of the actual content, to be the most positive interpretation of network neutrality. And so I’ll conclude by noting that I heard an interesting briefing today from Anagran, a hardware vendor offering flow-based traffic management (i.e., it doesn’t care what you’re doing, it’s just managing congestion). It’s being positioned as an alternative or supplement to Sandvine and the like, offering a way to try to keep P2P traffic manageable without having to do deep-packet inspection (and thus explicit discrimination).
The culture of service
I recently finished reading Punching In, a book by Alex Frankel. It’s about his experience working as a front-line employee in a variety of companies, from UPS to Apple. The book is focused upon corporate culture, the indoctrination of customer-facing employees, and how such employees influence the customer experience. And that got me thinking.
Culture may be the distinguishing characteristic between managed hosting companies. Managed hosting is a service industry. You make an impression upon the customer with every single touch, from the response to the initial request for information, to the day the customer says good-bye and moves on. (The same is true for more service-intensive cloud computing and CDN providers, too.)
I had the privilege, more than a decade ago, of spending several years working at DIGEX (back when all-uppercase names were trendy, before the chain of acquisitions that led to the modern Digex, absorbed into Verizon Business). We were a classic ISP of the mid-90s — we offered dial-up, business frame relay and leased lines, and managed hosting. Back then, DIGEX had a very simple statement of differentiation: “We pick up the phone.” Our CEO used to road-show dialing our customer service number, promising a human being would pick up in two rings or less. (To my knowledge, that demo never went wrong.) We wanted to be the premium service company in the space, and a culture of service really did permeate the company — the idea that, as individuals and as an organization, we were going to do whatever it took to make the customer happy.
For those of you who have never worked in a culture like that: It’s awesome. Most of us, I think, take pleasure in making our customers happy; it gives meaning to our work, and creates the feeling that we are not merely chasing the almighty dime. Cultures genuinely built around service idolize doing right by the customer, and they focus on customer satisfaction as the key metric. (That, by the way, means that you’ve got to be careful in picking your customers, so that you only take business that you know that you can service well and still make a profit on.)
You cannot fake great customer service. You have to really believe in it, from the highest levels of executive management down to the grunt who answers the phones. You’ve got to build your company around a set of principles that govern what great service means to you. You have to evaluate and compensate employees accordingly, and you’ve got to offer everyone the latitude to do what’s right for your customers — people have to know that the management chain will back them up and reward them for it.
Importantly, great customer service is not equivalent to heroics. Some companies have cultures, especially in places like IT operations, where certain individuals ride in like knights to save the day. But heroics almost always implies that something has gone wrong — that service hasn’t been what it needed to be. Great service companies, on the other hand, ensure that the little things are right — that routine interactions are pleasant and seamless, that processes and systems help employees to deliver better service, and that everyone is incentivized to cooperate across functions and feel ownership of the customer outcome.
When I talk to hosting companies, I find that many of them claim to value customer service, but their culture and the way they operate clash directly with their ability to deliver great service. They haven’t built service-centric cultures, they haven’t hired people who value service (admittedly tricky: hire smart competent geeks who also like and are good at talking to people), and they aren’t organized and incentivized to deliver great service.
Similarly, CDN vendors have a kind of tragedy of growth. Lots of people love new CDNs because at the outset, there’s an extremely high-touch support model — if you’ve got a problem, you’re probably going to get an engineer on the phone with you right away, a guy who may have written the CDN software or architected the network, who knows everything inside and out and can fix things promptly. As the company grows, the support model has to scale — so the engineers return to the back room and entry-level lightly-technical support folks take their place. It’s a necessity, but that doesn’t mean that customers don’t miss having that kind of front-line expertise.
So ask yourself: What are the features of your corporate culture that create the delivery of great customer service, beyond a generic statement like “customers matter to us”? What do you do to inspire your front-line employees to be insanely awesome?