BACKGROUND IMAGE: stock.adobe.com
Edge computing is attracting a lot of attention these days, even from cloud providers that have previously said “everything will go to the cloud.” For example, take AWS Outposts, a new service that AWS announced in November. This service, which should become available next quarter, enables customers to run AWS on-premises, and then connect to the AWS cloud. To accomplish this, AWS ships customers fully managed racks of AWS-designed compute and storage hardware running VMware.
But there’s more. AWS IoT SiteWise, part of a suite of IoT services, collects data from industrial sites through an on-premises gateway. The very next week, Microsoft announced new functionality for its own IoT service, Azure IoT Edge. Clearly, AWS and Microsoft now realize that the cloud alone will not be enough to provide the performance that enterprise IT and the growing number of applications for IoT will require.
The market interest from cloud providers, tech vendors and investors in edge computing is easy to understand: The global edge computing market was worth just shy of $8 billion in 2017 and is expected to surpass $20 billion by 2026, according to market research firm Stratistics MRC.
But that market interest is ultimately driven by a known technical weakness in public cloud-only models: performance. Applications, workloads and data sets that require a nearly instantaneous response function poorly when they are located far away from the users who are working with them. There’s nothing an engineer can do to transmit data faster than the speed of light, and the distances between large metro areas, multiple endpoints generating data and big cloud data centers are large enough to introduce significant latency, an issue that’s becoming even more acute with the growth of IoT.
As IoT continues to expand, users and applications will be generating more data than ever. But as effective as the cloud is for storage, the concept doesn’t work when it comes to delivering a fast response when there are great distances involved. And the availability of internet bandwidth in places where IoT and other remote devices are apt to be located can be quite performance-constrained.
When you consider how much data IoT will create — connected cars alone are expected to generate and use as much as 40 TB of data per vehicle per day — there are simply not enough pipes and bandwidth to move to and from the cloud with a low level of latency. Autonomous vehicles, for instance, can’t afford to wait seconds to send data to the cloud, process that data and receive an answer. By then, it may be too late to avoid a hazard or take a better route to the destination.
Enter the edge
Increasingly, large organizations are coming to the realization that a lot of processing and analytics power has to sit at the edge. It’s physically impossible to put it all in the cloud and expect to avoid latency issues.
Edge computing enables data to be aggregated at a local point of presence, ensuring a very high-performance, low-latency option for processing. It consists of smaller data centers in locations closer to where users are working. These enable them to communicate with data without the latency challenges.
Further, edge computing enables users to benefit from cloud elasticity and economics without the problems presented by distance. Cloud providers will likely extend their delivery models closer to the edge — or at least they should — because that’s where computing will increasingly be needed.
The edge, therefore, extends the cloud — especially for data access — closer to end users, where it can be consumed and managed as if it were stored locally. This way, applications can take advantage of all the cloud has to offer without any of the performance drawbacks.
It’s clear that edge computing is a critical component of a successful hybrid cloud strategy. As both data and its importance continues to grow, organizations need to begin building their edge computing strategies or risk missing out on the real opportunities IoT and the cloud have to offer.
All IoT Agenda network contributors are responsible for the content and accuracy of their posts. Opinions are of the writers and do not necessarily convey the thoughts of IoT Agenda.