Edge systems, networks and IoT have expanded rapidly — so quickly that IT teams face significant challenges in designing an overall architecture to manage edge deployments and integrate them within an enterprise IT structure. To build an edge architecture, IT leaders must pin down three critical areas:
-
What are the elements of a mature IT architecture?
-
What roles do IT and end users play in this scheme?
-
How does edge IT synergize with central IT?
Core elements of a mature edge architecture
A mature IT architecture is characterized by well-orchestrated workflows that enable compute at the edge as well as data exchanges between the edge and central IT. Throughout all processes, security must be maintained.
What do edge implementations look like in practice? Ideally, edge implementations feature mini-data centers — remote servers, networks and storage placed in edge locations that are self-contained to the point where a remote site can operate without having to share processing or storage capacity with others during regular operations.
The required data transfers between remote edge sites and central IT are carefully orchestrated, and IT is likely to install zero-trust networks so it can observe and secure all edge activities.
Conceptually, creating an IT architecture that incorporates both central IT and the edge sounds easy — but it isn’t. What must be achieved architecturally is a synergistic blend of hardware, software, applications, security and communications that work seamlessly together, whether the technology is at the edge or in the data center.
When multiple solutions and vendors are involved, the integration of these elements can be daunting — but the way that IT can address architectural conflicts upfront is by predefining the interface protocols, devices, and the hardware and software stacks.
Defining IT and end-user roles in a hybrid IT environment
In an overarching enterprise architecture that encompasses both corporate and edge IT, technical support for edge IT can be a challenge. Fortunately, an abundance of affordable software enables IT to remotely troubleshoot and repair many technology issues at the edge.
Unfortunately, however, not every edge IT issue can be resolved remotely. When on-site troubleshooting is required at the edge, there is the option of placing IT personnel at major edge sites so that technical help is readily on hand, and some companies do this.
However, a more common approach to on-site IT support for edge computing is to create a hybrid team of IT and tech-savvy users. Users trained in the basics of maintaining IT networks and assets can perform basic IT work at the edge, with the option of calling in IT for remote help or a physical visit when it is needed.
In the hybrid user-IT team approach, two types of user skillsets are typically required:
-
Application experts. Users knowledgeable in the edge applications running at the site.
-
Operational support. Tech-savvy users able to reboot routers and servers, identify personnel to be added to or subtracted from network access, and perform routine network monitoring and configuration.
Most edge site teams include “super users” who know the applications and can train other users. As for the rudiments of IT, tech-savvy users can be trained by IT in these skills and as noted, supported by IT as needed.
The hybrid approach is a win-win for everyone. It gives users a sense of autonomy, and it saves IT from making frequent trips to remote sites. The key to it all is to clearly define the roles that IT and end users will play in edge support. In other words, what are end-user technical support people in charge of, and at what point does IT step in?
2026 edge: AI and automated orchestration
One key to more autonomous edge computing is the use of AI algorithms that can enable at-the-site compute without having to go to IT resources that are not on the edge.
Examples include:
-
An autonomous sensor that monitors the environmental conditions of goods that must be stored at certain temperatures and humidities.
Another benefit that AI offers in manufacturing is the ability to literally run manufacturing operations on its own. Industrial robots, conveyer belts, QA checkouts and 3D manufacturing can be autonomously sequenced and run by AI in a 24/7 environment that requires few or no! workers to be present on the lines.
As these processes create data, the AI learns through its machine learning (ML) model how it can more expeditiously execute tasks and perform future QAs that are fine-tuned from “learning” about product failures and anomalies.
Synching edge systems with central IT
Self-contained edge computing can basically “run itself” during the day, thanks to dedicated processing, storage and systems that enable operations to run at full throttle. This reduces data communications costs because self-contained edges eliminate the need to continuously access offsite clouds and data centers, which saves bandwidth.
This edge self-containment strategy works well for retail outlets, remote manufacturing plants, and field offices — but there is still an ultimate need for remote edge sites to coordinate with and exchange data with offsite clouds and central data centers.
To effectuate data exchange, and also to maximize self-contained compute, most edge sites adopt a “store and forward” approach that caches data at the remote edge site during peak operations, and then later uploads data to centralized systems.
A majority of this upload work is done at night, but there are also cases when others in the enterprise need intra-day information from the edge. An example is a logistics tracking system that must route data in real time to everyone involved, no matter where. In other cases, only near-real-time information is needed, so data can be sent in periodic bursts during the day, when operations are less active, and bandwidth is more available.
The task for IT is to orchestrate these workflows and data exchanges within the context of an overall IT architecture. How each element is defined will determine where servers, storage, systems and databases are placed.
Disaster recovery and failover at the edge
Finally, a mature architecture must define disaster recovery. What happens if a remote edge site fails? A mature architecture must define where it fails over to, so the site can keep going even if its local systems are out.
In these cases, data and systems must be replicated for redundancy in the cloud or in the corporate data center, so remote sites can fail over to these resources, with end-to-end security in place at all points.
Articulating the hybrid strategy to business leadership
A mature IT architecture encompasses both central IT and edge IT. It must minimally define IT resource allocations, workflow directions, and even the people throughout the enterprise (including the edge) who will play important IT roles in this architecture.
Because edge users will be involved, the development and ongoing support of IT architecture becomes a group effort. IT might know the best practices for maximizing IT assets, but it is users who understand the operational metrics that must be met, and who must step in locally when edge IT problems arise.
This makes it incumbent on IT leadership to clearly articulate enterprise IT architecture to the C-level, the board, user managers and IT itself — because executing this hybrid architecture requires all hands to be on board.
