Rupert, an inspiring post, thanks.
This playing field is still foggy to me, and I'm having some difficulties seeing the center fielder from home plate.
Correct me where I go astray. From what you are saying, AKAM introduces a layer of caching atop [or is it instead of?] the normal ASP functions of EXDS, in this case, by allowing the user to also direct flows to AKAM servers which are located in their own [AKAM] server farms in their own [AKAM] POPs? Where are these AKAM servers located, typically?
That would mean that there is an additional layer of infrastructure platforming involved, and from yet additional (read: additional routes involved) locations, all being serviced by... the open 'net?
Or, are the AKAM flows handled over dedicated pipes between their POPs? Or perhaps they are handled by SP's ATM flows, or tunneled in some way, so as to isolate them from normal congestion anomalies associated with the open net?
In the scenario you presented, I am also curious to know who pays AKAM, the enterprise user, or EXDS, or is this optional?
You pay EXDS to host your web server and provide you with services to keep it up and runnig, and so on, so your content is always available to users. You pay AKAM to flow your content through their servers around the world (which AKAM has placed at a variety of data centers including EXDS).
TIA, and Regards, Frank Coluccio |
