Akamai Case
I. Statement of Problem
Akamai’s edge servers completely revolutionize the way internet content is delivered to the end user. However, “because of the diverse programming methods used by websites, transferring the data to Akamai’s edge servers will add complexity to both set-up and maintenance.” (Xanedu Courspack, PG 88). Two of the strategic questions that Akamai faces are as follows. First, should it keep the status quo of working with all web server platforms, or should it align with one partner? Second, going forward with the more involved EdgeSuite product, should Akamai increase its in-house sales force, rely totally on resellers, i.e. system integrators, hosting firms, and network carriers, or some combination of both? II. Critical Issues
Internet Architecture 1. With the Internet’s rapid growth and “network of networks” architecture, users sometimes experienced slow transaction processing at e-commerce sites and were unable to access Web sites that had been inundated with user “hits.” 2. The Internet was vulnerable to the loss of data packets as they were routed through the network of networks. 3. Performance problems were due to bottlenecks in four major areas: a. First-mile infrastructure having to cope with heavy traffic loads as a Web site’s audience grew. b. Backbone networks causing normal processing delays as traffic passed through an average of 17 to 20 routers en route to its destination. c. Peering for global data delivery but no one’s network reached into every market. d. Last –mile infrastructure straining an IAP’s router or modem capacity to the point that users might not be able to connect to the Internet at all.
Challenges 1. As most leading enterprise software companies are now offering platforms (which all have proprietary features) for creating and managing Web services, Akamai has to decide which side of the business “camps” they will want to be on: Java camp or .NET.
Akamai’s edge servers completely revolutionize the way internet content is delivered to the end user. However, “because of the diverse programming methods used by websites, transferring the data to Akamai’s edge servers will add complexity to both set-up and maintenance.” (Xanedu Courspack, PG 88). Two of the strategic questions that Akamai faces are as follows. First, should it keep the status quo of working with all web server platforms, or should it align with one partner? Second, going forward with the more involved EdgeSuite product, should Akamai increase its in-house sales force, rely totally on resellers, i.e. system integrators, hosting firms, and network carriers, or some combination of both? II. Critical Issues
Internet Architecture 1. With the Internet’s rapid growth and “network of networks” architecture, users sometimes experienced slow transaction processing at e-commerce sites and were unable to access Web sites that had been inundated with user “hits.” 2. The Internet was vulnerable to the loss of data packets as they were routed through the network of networks. 3. Performance problems were due to bottlenecks in four major areas: a. First-mile infrastructure having to cope with heavy traffic loads as a Web site’s audience grew. b. Backbone networks causing normal processing delays as traffic passed through an average of 17 to 20 routers en route to its destination. c. Peering for global data delivery but no one’s network reached into every market. d. Last –mile infrastructure straining an IAP’s router or modem capacity to the point that users might not be able to connect to the Internet at all.
Challenges 1. As most leading enterprise software companies are now offering platforms (which all have proprietary features) for creating and managing Web services, Akamai has to decide which side of the business “camps” they will want to be on: Java camp or .NET.