Edge computing

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Edge computing is a method of optimizing applications or cloud computing systems by taking some portion of an application, its data, or services away from one or more central nodes (the "core") to the other logical extreme (the "edge") of the Internet which makes contact with the physical world or end users. [1] In one vision of this architecture, specifically for IOT devices, data comes in from the physical world via various sensors, and actions are taken to change physical state via various forms of output and actuators; by performing analytics and knowledge generation at the edge, communications bandwidth between systems under control and the central data center is reduced. Edge Computing takes advantage of proximity to the physical items of interest also exploiting relationships those items may have to each other. Another, more broad way of looking at "Edge Computing" is to put any type of computer program that needs low latency nearer to the requests.

In some cases Edge computing requires leveraging resources that may not be continuously connected to a network such as autonomous vehicles, implanted medical devices, fields of highly distributed sensors, and mobile devices.[2] Edge computing covers a wide range of technologies including wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing,[3] mobile edge computing,[4][5] cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented reality, the Internet of Things (IoT) and more.[6] Edge Computing can involve Edge nodes directly attached to physical inputs and output or Edge Clouds that may have such contact but at least exist outside of centralized Clouds closer to the Edge.

Other time-sensitive applications that can benefit from edge-compute include authentication, log-filtering, data aggregation, image re-sizing, e-commerce personalization, and TLS (HTTPS) session setup.


Edge computing pushes applications, data and computing power (services) away from centralized points to the logical extremes of a network. Edge computing takes advantage of microservices architectures to allow some portion of applications to be moved to the edge of the network. While Content Delivery Networks have moved fragments of information across distributed networks of servers and data stores, which may spread over a vast area, Edge Computing moves fragments of application logic out to the edge. As a technological paradigm, edge computing may be architecturally organized as peer-to-peer computing, autonomic (self-healing) computing, grid computing, and by other names implying non-centralized availability.

To ensure acceptable performance of widely dispersed distributed services, large organizations typically implement edge computing by deploying server farms with clustering and large scale storage networks. Previously available only to very large corporate and government organizations, edge computing has disseminated technology advances and cost reductions from large-scale implementations and made the technology available to small and medium-sized businesses.[7] Small, low-cost cluster hardware and freely-available cluster management software have increased accessibility.

The target of Edge Computing is any application or general functionality needing to be closer to the source of the action where distributed systems technology interacts with the physical world. Edge Computing does not need contact with any centralized Cloud. Edge Computing does use a similar or the same distributed systems architecture as centralized Clouds but closer to or directly at the Edge.

Edge computing imposes certain limitations on the choices of technology platforms, applications or services, all of which need to be specifically developed or configured for edge computing.[8]


Possible advantages of edge computing are:

  1. Edge application services significantly decrease the volumes of data that must be moved, the consequent traffic, and the distance the data must travel, thereby reducing transmission costs, shrinking latency, and improving quality of service (QoS).
  2. Edge computing eliminates, or at least de-emphasizes, the core computing environment, limiting or removing a major bottleneck and a potential single point of failure.
  3. Ability to ride the same cost curves and improvements by exploitation of the same architecture and fundamental underlying computing technologies as other Clouds whether centralized fee-for-service Clouds or closed private clouds which are also centralized. Cost accounting models based upon how shared resources are billed in fee-for-service clouds (timesharing) often expressed by the phrase "as a Service" should not be confused with the common architectural basis of centralized Clouds, Edge Clouds, and increasingly Edge nodes as well. Ultimately all IT systems, distributed or not, must provide viable services regardless of how or where they are implemented. Clouds, however, do share common distributed system architecture and technology forming three modes defined by distance from the edge: Centralized Clouds, Edge Clouds, and Edge nodes taken collectively also known as fog computing.

ISO/IEC 20248 provides a method whereby the data of objects identified by edge computing using Automated Identification Data Carriers [AIDC], a barcode and/or RFID tag, can be read, interpreted, verified and made available into the "Fog" and on the "Edge" even when the AIDC tag has moved on.


  1. Edge computing must be designed to work in the face of sporadic availability/connectivity of edge compute nodes, since edge nodes may only have power available sporadically.
  2. Edge computing requires applications to be built for horizontal scalability. Generally the recommendation is to build applications that follow the 12-factor application guidelines.[9]
  3. Edge computing requires operations to be able to deploy to a distributed set of edge nodes, coordinate cross-node state and storage, or handle inconsistent state gracefully.

Grid computing[edit]

Edge computing and grid computing are related. Whereas grid computing overlies network structure to serve a primary function, such as a particular application, Edge computing involves that part of the Internet most directly in touch with sensing or altering the adjacent physical world. Edge and grid computing both link closely related systems and storage, but Edge computing connects with the physical world as a point of emphasis, while grid computing interconnects strictly on a functional basis.[citation needed]

See also[edit]


  1. ^ Garcia Lopez, Pedro; Montresor, Alberto; Epema, Dick; Datta, Anwitaman; Higashino, Teruo; Iamnitchi, Adriana; Barcellos, Marinho; Felber, Pascal; Riviere, Etienne (2015-09-30). "Edge-centric Computing: Vision and Challenges". ACM SIGCOMM Computer Communication Review. 45 (5): 37–42. doi:10.1145/2831347.2831354. ISSN 0146-4833. 
  2. ^ Gaber, Mohamed Medhat; Stahl, Frederic; Gomes, Joao Bártolo (2014). Pocket Data Mining - Big Data on Small Devices (1 ed.). Springer International Publishing. ISBN 978-3-319-02710-4. 
  3. ^ Skala, Karolj; Davidović, Davor; Afgan, Enis; Sović, Ivan; Šojat, Zorislav (2015). "Scalable Distributed Computing Hierarchy: Cloud, Fog and Dew Computing". Open Journal of Cloud Computing (OJCC). RonPub. 2 (1): 16–24. ISSN 2199-1987. Retrieved 1 March 2016. 
  4. ^ "Mobile-Edge-Computing White Paper" (PDF). ETSI. 
  5. ^ Ahmed, Arif; Ahmed, Ejaz. A Survey on Mobile Edge Computing. India: 10th IEEE International Conference on Intelligent Systems and Control(ISCO’16), India. 
  6. ^ Edge Computing - Pacific Northwest National Laboratory
  7. ^ Felde, Christian. "On edge architecture". 
  8. ^ Gai, Keke; Meikang Qiu; Hui Zhao; Lixin Tao; Ziliang Zong (2016). "Mobile cloud computing: Dynamic energy-aware cloudlet-based mobile cloud computing model for green computing". 59: 46–54. doi:10.1016/j.jnca.2015.05.016.  PDF
  9. ^ Wiggins, Adam. "The Twelve-Factor App". 12factor.net. Retrieved 2018-07-31. 

Further reading[edit]