Edge can be divided into the Device Edge and the Infrastructure Edge. This presentation discusses how to leverage the Infrastructure edge in modern software architecture.

1. Cloud to Edge:
Architecting for the
Next Generation of the
Internet
WESLEY REISZ
VP Technology at Section
Chairperson QCon SF &
Co-host of The InfoQ Podcast

2. Toyota predicts that the car-to-cloud data stream will reach 10 exabytes per month by 2025.
~2 million vehicles sold in North America alone

3. WESLEY REISZ
VP Technology @Section.io
Chairperson QCon SF &
Co-host of The InfoQ Podcast
wes@sec&on.io
@wesreisz

4. Section is a developer-focused Edge
Compute Platform for deploying
containerized workloads at the edge.

5. DEFINE EDGE
Edge overloaded term
ARCHITECTURE
Let’s compare what things look like
in and outside of an Edge Native Architecture
CLOUD NATIVE LESSONS
AT THE EDGE
DevOps, ELK, K8s, Containers

6. Now is the Mme to adopt an edge na've
strategy at the device and infrastructure
edge that is flexible, leverages DevOps,
and offers deep insights into the
opera7on.
TL;DR

7. DEFINING THE EDGE

10. LASTMILE
DEVICE
EDGE
INFRASTRUCTURE
EDGE
Self-contained
end-point devices, such
as smart-phones, wearables and
automobiles.
Gateway devices such as IoT
aggregators, switching and routing
devices.
On-premise server platforms.
Access sites which house
network access equipment,
such as cellular radio base
stations, xDSL and xPON access
sites.
Aggregation hubs, such as those which house DAS (Distributed
Antenna Systems) and serve as an initial aggregation of
transmission connections from the access sites.
Regional data centers and central offices, where access controller,
switching equipment and other service gateway functionality

11. CENTRALIZED
CLOUD
INFRASTRUCTURE
EDGE
DEVICE
EDGE
IOT/
SENSORS
High Latency / More ComputeLower Latency / Less Compute

13. A content delivery network or content distribution network (CDN) is a
geographically distributed network of proxy servers and their data centers.
The goal is to provide high availability and high performance by distributing
the service spatially relative to end-users…
CDNs are a layer in the Internet ecosystem. Content owners such as media
companies and e-commerce vendors pay CDN operators to deliver their
content to their end users. In turn, a CDN pays ISPs, carriers, and network
operators for hosting its servers in their data centers.
Edge Compute Platform
compute
, and custom workloads
,
^
Edge Compute Platforms Application Developers
ensure workloads
are running between their servers and users.
An edge compute platform leverages available compute between the cloud
provider and the user (together with cloud devops practices) to deploy
traditional CDN & custom workloads.

14. Use Cases
Facebook Live:
Stream is sent via RTMPS (Real-Time Messaging Protocol) to a geographically local PoP. The
connection is forwarded over an internal Facebook network to a Facebook data-centre. When
you see a live stream in your feed and you click on it the player requests the manifest. If it isn't
already on your local PoP the request goes to the data centre to get the manifest, and then
fetches the media files in 1 sec clips. As they get sent back they are cached on the PoP if they
aren’t there already.
https://www.infoq.com/podcasts/sachin-kulkarni-facebook-live/
Cloudflare:
Service Worker API implementation for the Cloudflare platform. Brings a server less style
approach to running JavaScript workloads on their Points of Presence.
https://www.infoq.com/presentations/cloudflare-workers/
Chick fil-A:
We think of our Edge Computing environment as a “micro private cloud”. By this, we mean that
we provide developers with a series of helpful services and a place to deploy their applications
on our infrastructure.
https://medium.com/@cfatechblog/edge-computing-at-chick-fil-a-7d67242675e2
Tesla:
A Virtual Power Plant (VPP) is a network of distributed energy-resources (often solar, wind, and
batteries) that are aggregated to provide smarter and more flexible power generation,
distribution, and availability. Tesla's VPP consists of vertically integrated hardware and
software, including both cloud and edge computing.
https://qconlondon.com/london2020/presentation/tesla-virtual-power-plant
Infrastructure Edge Compute

15. h8ps://landscape.lfedge.org
Landscape

16. TRADITIONALAPPLICATION
ARCHITECTURE

21. BOT
WAF

22. BOT WAF

23. CAPEX
OPEX
vs.

24. CHALLENGES
Shared infra
Limited Choice (often one size fits all)
Often Little insight into what’s happening

25. EDGE-NATIVE APPLICATION
ARCHITECTURE

26. Points of Presences (POPs or Clusters)
•OpEx vs CapEx
•Dynamic
•Multi-provider (all cloud vendors
DigitalOcean, RackCorp, CenturyLink, Packet)
•Built on Top of the same technologies and
practices as the cloud
•Containerized

27. Modules
•Unit of deployment is the container
•Can horizontally scale workloads
•Configuration is simplified
•Choice of vendors without locking
•Your own code can be deploy
WAF
BOT
Container

28. CHALLENGES
Orchestration of these containers
Applying the DevOps Practices
Insight into what’s happening
Connectivity

29. LESSONS FROM THE CLOUD
ATTHE INFRA EDGE

30. Flexibility
Configurable, ubiquitous,
multi cloud/ multi provider
DevOps Practices
Continuous delivery/automation/
containerized workload
Insights and Visibility
Understanding what’s happening
with your system Observability

31. Developers need the ability to package and
deploy workloads wherever they need logic to
reside. They also need the tools to abstract the
complexity of deploying to multiple edge
locations.
We call this Any Workload, Any Where
Flexibility

32. RUNNING CONTAINERS
… is a standard unit of software that packages up code and all
its dependencies so the application runs quickly and reliably
from one computing environment to another
Provides the isolation / dependencies /
security
Standardized
Lightweight

33. KUBERNETES
Kubernetes Namespaces allows Isolation
… is an open-source container-orchestration system for
automating application deployment, scaling, and management.
It was originally designed by Google, and is now maintained by
the Cloud Native Computing Foundation.
Manages the horizontal scale / availability
Complicated, but understood at the cloud

34. MULTIPROVIDER DEPLOYMENTS
Terraform, bash, API/CLI
New languages/Tools (DarkLang and
Pulumi)
Infrastructure as code (IaC) is the process of managing and
provisioning computer data centers through machine-readable
definition files, rather than physical hardware configuration or
interactive configuration tools. The IT infrastructure managed
by this comprises both physical equipment such as bare-metal
servers as well as virtual machines and associated
configuration resources.

35. AWS
Packet
CenturyLink
???

36. AWS
Packet
CenturyLink
???

37. DevOps is the combination of cultural philosophies,
practices, and tools that increases an organization’s ability to
deliver applications and services at high velocity: evolving
and improving products at a faster pace than organizations
using traditional software development and infrastructure
management processes.
This speed enables organizations to better serve their
customers and compete more effectively in the market.
You Build, You Own It
DevOps Practices

38. API DRIVEN
… able to write code to control aspects of the system.
Customizable
Open
Integration

39. GITOPS
… is a way of implementing Continuous Deployment for cloud
native applications. It focuses on a developer-centric
experience when operating infrastructure, by using tools
developers are already familiar with, including Git and
Continuous Deployment tools.
Githooks
Trigger message deployments to global
POPS
Configuration management

41. Code/Config
Cloud Service
Message Bus
Global POPs
Git

42. Things will eventually go wrong. When they do,
developers need the ability to dive into the stack and
understand what is happening. It should be familiar
and combine the power of search and visualization.
Insights and Visibility

43. OBSERVABILITY
In control theory, observability is a measure of how well
internal states of a system can be inferred from knowledge of
its external outputs. The observability and controllability of a
system are mathematical duals
3 Pillars of Observability :
• Logs
• Metrics
• Tracing

44. WAF
BOT
Container

49. Connectivity… we can only go so far today. K8s needs
connectivity. There are projects (such as Project EVE
K3s, KubeEdge) that are pushing orchestration into
the device edge.
Challenges Remaining

50. DEFINE EDGE
Edge overloaded term
ARCHITECTURE
Let’s compare what things look like
in and outside of an Edge Native Architecture
DevOps, ELK, K8s, Containers
CLOUD NATIVE LESSONS
AT THE EDGE

51. KEY TAKEAWAYS
•Edge is divided into two groups defined by the last mile. On one
side is the device edge and the other is the Infrastructure edge.
•Traditional applications have used CDN as a blackbox but more
can be done by applying some of the lessons learned at the
Cloud.
•Challenges exist in leveraging cloud native practices at the
Infrastructure edge; however, it is possible to leverage DevOps to
address many of these issues.

53. An Industry Ripe for Disruption
Realizing the full potential of the Edge needs a catalyst
- software developers -

54. QUESTIONS
WESLEY REISZ
VP Technology at Section
Chairperson QCon SF &
Co-host of The InfoQ Podcast
wes@sec&on.io
@wesreisz

55. BACKUP SLIDES

56. Serverless
Container
MODULES
Web App Firewall (WAF)
Signal Sciences
ThreatX
Templarbit
Shield
Image Optimization
Kraken
Cloudinary
Cache
Varnish 3-6
Bot Blocker
PerimeterX Bot Blocker
Imperva/ Distil Bot
Blocker
Code
Node.js
OpenResty (Lua/nginx)
Bring Your Own
A/B Testing
SiteSpect
Containerized Apps
Serverless Apps