Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Edge Compute for Network Services vs Application Workloads

· 1 min read · Peer1IX Team

Edge Compute for Network Services vs Application Workloads

Not all edge compute is the same. Network functions and application workloads have different needs. How to plan each.

Two kinds of edge workload

Network functions — routers, firewalls, SD-WAN gateways — sit in the path of traffic and process packets. Application workloads — caches, game servers, APIs — serve users.

Different requirements

Network functions need high packet-per-second performance, low latency and direct attachment to the network. Applications need balanced CPU, memory and storage, and often specific hardware like GPUs.

Placement

Network functions must be where traffic flows: at the meeting points of circuits and clouds. Applications should be close to their users.

Matching services

  • Use Peer1ix Virtual Edge for network functions attached directly to the fabric.
  • Use Edge Data Centers for your own servers running application workloads.

Combine them

A typical edge design uses both: a virtual SD-WAN hub and firewall on Virtual Edge, and application servers in edge colocation, all connected through the fabric.

edge computenetwork servicesapplications