Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Best of 2016 Recommended by Editor Recommended by Reviewer Recommended by Reader
Search
Survey on fog computing
Hu P., Dhelim S., Ning H., Qiu T.  Journal of Network and Computer Applications 98 (C): 27-42, 2017. Type: Article
Date Reviewed: Apr 3 2019

In the Internet of things (IoT), is there a difference between edge and fog computing?

By now we all understand the cloud computing paradigm in which end devices (anything from sensors and smartphones to industrial robots or cars) connect to highly scalable computing facilities run by someone else and accessible through classic Internet protocols. It is also easy to grasp that for applications with a strong demand for real-time, low-latency, high-bandwidth, or very secure communications, sending each request up to the cloud and waiting for a response will not provide a satisfying user experience.

Today’s most prominent architectural pattern to overcome this shortcoming is to move computation (and storage) closer to the end devices, toward the so-called edge of the cloud or the network. So it seems quite natural to call this architecture “edge computing” and the actual systems performing the computation in proximity to the end devices “edge nodes.”

The paper also subscribes to this view, albeit defining it as “fog computing.” Consequently, it faces insurmountable difficulties when trying to separate the fog from the edge, arriving at extraordinarily strange if not flatly wrong characterizations, such as edge computing “is located in end devices” or unable to support “multiple IoT applications.”

Amusingly, in many places, the actual technical content openly hints at the true differences, for instance, when talking about software-defined networking (SDN), network function virtualization (NFV), cross-node management capabilities, and various prototypical fog applications. The authors simply (and utterly) fail to correctly analyze their own data and to formulate a correct definition consistent with it. This is also egregiously evident in the two abysmally trivial architecture diagrams and the dreadfully incoherent definition attempts of various terms (fog platform, fog layer, fog node, edge node, end node).

Disregarding this, and also discounting the fact that the paper is too long by some 30 percent, the reader will find a lot of features correctly attributed to fog computing that are typically absent in pure edge computing. If you do not want to embark on this search and rescue mission, I would recommend looking up the National Institute of Standards and Technology’s (NIST’s) “Fog computing conceptual model” instead [1].

Reviewer:  Christoph F. Strnadl Review #: CR146509
1) Iorga, M.; Feldman, L.; Barton, R.; Martin, M. J.; Goren, N.; Mahmoudi, C. Fog computing conceptual model. NIST Special Publication 500-325, March 2018, https://doi.org/10.6028/NIST.SP.500-325.
Bookmark and Share
  Reviewer Selected
Editor Recommended
Featured Reviewer
 
 
Distributed Networks (C.2.1 ... )
 
 
Centralization/ Decentralization (K.6.4 ... )
 
 
Distributed Objects (D.2.12 ... )
 
 
Distributed Systems (C.2.4 )
 
 
Distributed Systems (D.4.7 ... )
 
 
Distributed Systems (H.3.4 ... )
 
  more  
Would you recommend this review?
yes
no
Other reviews under "Distributed Networks": Date
Fog computing: concepts, frameworks and technologies
Mahmood Z.,  Springer International Publishing, New York, NY, 2018. 291 pp. Type: Book (978-3-319948-89-8)
Mar 6 2019
State-of-the-art, challenges, and open issues in the integration of Internet of things and cloud computing
Díaz M., Martín C., Rubio B.  Journal of Network and Computer Applications 67(C): 99-117, 2016. Type: Article
May 10 2017
A gap analysis of Internet-of-Things platforms
Mineraud J., Mazhelis O., Su X., Tarkoma S.  Computer Communications 89(C): 5-16, 2016. Type: Article
May 5 2017
more...

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright © 2000-2019 ThinkLoud, Inc.
Terms of Use
| Privacy Policy