CDNs - the rise of the anticloud

I was at a meeting with Akamai the other day. Akamai is a very fascinating company and i have followed both their business and technology progress quite closely. in fact, I have made money on their stock. Akamai has been delivering services in the Cloud business model for longer than the term Cloud has been in existence. In a strange way, though, I consider them anticloud. They are a force driving decentralization of content while Cloud is the force of centralization of both content and processing. In many ways Akamai is stretching the boundaries of the Cloud to the edges and in an extreme situation right to the home. This extreme situation is when CDNs merge with P2P technologies to deliver content from the end points themselves. Now, if anybody thinks this is hypothetical and fantasy then, look at Red Swoosh acquisition by Akamai. What P2P lacks, arguably, is the content management sophistication of traditional CDNs but companies like Akamai see no reason why the management cannot be extended to a content delivery node sitting on any of home network devices viz., wifi router, broadband router, set-top box etc.

In principle, this may allow some users to become data center providers for their community where the service is delivered by Akamai through its partners but the real estate is rented from end-users who make the capital investment into buying bigger network devices.

The forces pushing the content to the edges are not new - network congestion which gets exacerbated by rise of video. Today's digital video is not your father's video content. It is much bigger in resolution, higher in frame rates, interactive, 3D etc. All these factors demand data capacity of unprecedented levels. A 4K video (which you can upload on youtube now and is actually a resolution of 4096x3072) will not take a lot of simultaneous viewers to clog the internet backbone. Through the history of the internet, the last mile has been the bottleneck but with the advent of video the rate limiting characteristic of the last mile is preventing the meltdown of the internet. Thank god, we don't have all the internet users on broadband !! It is easy for people who have seen Indian cities transform in last 10 years to relate with this. The prosperity has resulted in explosion of car ownership but the roads have failed to keep pace and result is massive traffic jams.

It is no surprise that Cloud providers are launching or looking to launch their own CDNs. It is not easy though to build out POPs across the globe even for large companies. For video the Cloud will be distributed and stretched to include the homes. It is the management of content that will be Cloud based but the data is more likely to reside on the edges. Microsoft has over a period of time has moved away from using Akamai and Limelight networks to owning CDN assets on the edges and Azure CDN i believe is totally MSFT owned now.

Things are getting really interesting in this space and it may be time to go long on Akamai again but at $40+ it is a little too high for me.

Strange use of my profile data on Gmail…….

Yesterday I sent out a calendar invite to the CTO of a well known cloud computing startup. When I view the response on Outlook on my PC, I see the acceptance email addressed to my Gmail address.



The acceptance email from this person on my iPhone was addressed to a friend of mine. On iPhone when I click on this friend’s name on the “to” field I see his Gmail address and my Gmail address in the details about my friend.

Now all this is very confusing because I sent my calendar invite from my work email and not Gmail. There is a connection though, I have set my work email as the forwarding address for the emails that I receive on my Gmail that match a set of filter criteria. More specifically, I have Google Alerts directed to my Gmail account and I forward those alerts to my work email address. Another important fact is that this startup Company is using Gmail for their corporate email.

So it is clear that when I send a calendar invite from my work email account to the personnel of this company it hits the Gmail servers. Gmail at that point is using my work email address to look up my personal Gmail account and is sending the responses to both my work email and my Gmail account. This is a big data privacy and security issue. When enterprises worry about moving their applications and data to the Cloud it is these kinds of leaks (inadvertent or otherwise) that they fear and rightly so.

In the traditional IT model, the likelihood of such events is low as there is clear physical and ownership separation of my personal data and my enterprise data. Google has a natural desire to maintain a single identity across all my aliases/accounts, which may or may not be a desired state for me. The massive analytics infrastructure operates across all data regardless of their ownership/tenancy boundaries.

While this may allow Google to offer valuable products and services to me, like highly personalized search results and recommendations, it exposes more information than I am comfortable disclosing and worst of all I don’t even fully understand what it might expose. This is a small but illustrative example that shows why it is imperative that enterprises follow the model of “trust but verify” with Cloud providers when engaging them. Cloud providers must share and expose their architectural details for 3rd party audit. There may be a case for identifying functions that are more prone to creating privacy/security risks like analytics which by design are meant to extract identifiable information from a large data sets regardless of tenant boundaries. These functions and their output data access should be controlled and controls should be made transparent. In fact, enterprise tenants should be able specify and verify what functions are allowed with specific data - like analytics. Consumers have little leverage with large Corporates since we consumers value the functionality delivered by these companies far more than the potential loss of privacy/security so we are unlikely to vote with our mouse clicks.

my iPhone mail and calendering application has a bug

I showed up exactly 3 hours late for a meeting. I was traveling from East Coast to the West Coast. Two things happened. Actually one happened and one didnot. My iPhone time automatically changed to PST. But, the calendar was still operating on EST as it requires an explicit change of zone.

Now things get interesting as the alerting functionality was picking up the time from iPhone time. So i was getting alerts for a personal reminder i had set at 10.00 EST each day at 10.00 PST. For some reason I did not notice this error. I think the reason is that time zone shift hadn't happened totally in my mind. For this particular reminder I actually did want to be reminded at 10.00 AM local time and that is what i was getting so I didnot find anything amiss. In fact, this behaviour lulled me into thinking that all was correct.

A consistent and correct solution is for all the functions in email and calendering appplications (and all linked applications) to pick time and zone data from a single source. If there are multiple sources user should be warned about conflicts.

Note to self, always manually change the time zone or switch the time zone support to "off"