Click Below to Get the Code

Browse, clone, and build from real-world templates powered by Harper.
Blog
GitHub Logo

Reflections, Edge Computing 2022

Perspective on edge computing in 2022 and how the industry has not reached the point where edge is as easy as cloud, but progress has been made.
Blog

Reflections, Edge Computing 2022

Aleks Haugom
Senior Manager of GTM
at Harper
October 11, 2022
Aleks Haugom
Senior Manager of GTM
at Harper
October 11, 2022
Aleks Haugom
Senior Manager of GTM
at Harper
October 11, 2022
October 11, 2022
Perspective on edge computing in 2022 and how the industry has not reached the point where edge is as easy as cloud, but progress has been made.
Aleks Haugom
Senior Manager of GTM

Last week we took a team of ten to the Edge Computing Expo in Santa Clara, CA. The conference had excellent speakers and an array of companies spanning the edge industry. We saw hardware, AI software, and even Boston Dynamics' favorite yellow dog. 

Complexity is Still the Norm

What stuck out to us was the number of companies still looking for product market fit. Like early cloud computing, the edge computing industry is still young. Although early industry leaders are emerging, most companies are yet to find a solid product-market fit. We see plenty of investment in edge infrastructure, but moving the edge beyond DIY is still in its early stages. Today, there are few solutions that abstract away the complexity of edge to make development easy.

Mind-Blowing Growth Projections

In a recent report, 451 Research or S&P Global predicted a 85% CAGR for the edge IaaS market over the next five years, bringing the industry to $29.9 billion compared to the $738 million earned in 2021. Critical to meeting this industry valuation is our collective ability to offer easier-than-cloud solutions. Let's face it, for most use cases, cloud is sufficient. Therefore to entice more companies to benefit from edge, we need more than cool sensors and servers in every city; we need to make edge easy for every developer to access. 

Easier Than Cloud

At the Edge Computing Expo, one could get the impression that edge exists in a vacuum. However, it does not. Instead, it exists in a gradient between on-prem, edge, and cloud. Market leaders will inevitably be those that offer solutions across the spectrum.

My impression at the expo was that the edge's accessibility for those outside of the 10% of highly technical early adopters is still limited. Closing the edge-to-market gap requires more than just infrastructure. It requires that edge is easier than cloud. 

Jaxon Repp, Harper's Head of Product, speaking to Jake Cohen about Harper at the Edge Computing Expo.

About Harper

Harper's globally distributed database and application platform is orders of magnitude faster and more flexible than last-generation alternatives. Spanning the spectrum of delivery options, Harper is a vendor-agnostic solution giving developers the power to deploy anywhere from the cloud to the edge and even on-prem. With built-in cross-planet table level pub/sub, your data is always up to date across the globe regardless of vendor, ensuring near-zero global latency. Additionally, with Harper's lightning-fast memory map and high throughput potential, most companies reduce their infrastructure costs by at least 50% by switching to Harper. 

If you are interested in learning more, request a demo

Last week we took a team of ten to the Edge Computing Expo in Santa Clara, CA. The conference had excellent speakers and an array of companies spanning the edge industry. We saw hardware, AI software, and even Boston Dynamics' favorite yellow dog. 

Complexity is Still the Norm

What stuck out to us was the number of companies still looking for product market fit. Like early cloud computing, the edge computing industry is still young. Although early industry leaders are emerging, most companies are yet to find a solid product-market fit. We see plenty of investment in edge infrastructure, but moving the edge beyond DIY is still in its early stages. Today, there are few solutions that abstract away the complexity of edge to make development easy.

Mind-Blowing Growth Projections

In a recent report, 451 Research or S&P Global predicted a 85% CAGR for the edge IaaS market over the next five years, bringing the industry to $29.9 billion compared to the $738 million earned in 2021. Critical to meeting this industry valuation is our collective ability to offer easier-than-cloud solutions. Let's face it, for most use cases, cloud is sufficient. Therefore to entice more companies to benefit from edge, we need more than cool sensors and servers in every city; we need to make edge easy for every developer to access. 

Easier Than Cloud

At the Edge Computing Expo, one could get the impression that edge exists in a vacuum. However, it does not. Instead, it exists in a gradient between on-prem, edge, and cloud. Market leaders will inevitably be those that offer solutions across the spectrum.

My impression at the expo was that the edge's accessibility for those outside of the 10% of highly technical early adopters is still limited. Closing the edge-to-market gap requires more than just infrastructure. It requires that edge is easier than cloud. 

Jaxon Repp, Harper's Head of Product, speaking to Jake Cohen about Harper at the Edge Computing Expo.

About Harper

Harper's globally distributed database and application platform is orders of magnitude faster and more flexible than last-generation alternatives. Spanning the spectrum of delivery options, Harper is a vendor-agnostic solution giving developers the power to deploy anywhere from the cloud to the edge and even on-prem. With built-in cross-planet table level pub/sub, your data is always up to date across the globe regardless of vendor, ensuring near-zero global latency. Additionally, with Harper's lightning-fast memory map and high throughput potential, most companies reduce their infrastructure costs by at least 50% by switching to Harper. 

If you are interested in learning more, request a demo

Perspective on edge computing in 2022 and how the industry has not reached the point where edge is as easy as cloud, but progress has been made.

Download

White arrow pointing right
Perspective on edge computing in 2022 and how the industry has not reached the point where edge is as easy as cloud, but progress has been made.

Download

White arrow pointing right
Perspective on edge computing in 2022 and how the industry has not reached the point where edge is as easy as cloud, but progress has been made.

Download

White arrow pointing right

Explore Recent Resources

Comparison
GitHub Logo

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Cache
Comparison
End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Person with short dark hair and moustache, wearing a colorful plaid shirt, smiling outdoors in a forested mountain landscape.
Aleks Haugom
Senior Manager of GTM
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Jun 2026
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Comparison

Kafka-Centered Stacks vs. a Single Harper Cluster: Where Real-Time Latency Actually Comes From

End-to-end latency in real-time pipelines comes from coordination across systems, not from any single component. Four common workloads, tested two ways, show where multi-hop architectures compound delays and where collapsing storage, messaging, and compute into one runtime changes the math.
Aleks Haugom
Tutorial
GitHub Logo

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Cache
Tutorial
Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Person with very short blonde hair wearing a light gray button‑up shirt, standing with arms crossed and smiling outdoors with foliage behind.
Kris Zyp
SVP of Engineering
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp
Jun 2026
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp
Tutorial

Your API cache is secretly a database

Most teams treat a cache as a black box: URL-keyed blobs with a TTL, useful for speed and nothing else. In Harper, cached data lands in a real table inside the same query engine. That means filtering, joining, real-time subscriptions, and vector search all work against it.
Kris Zyp
Tutorial
GitHub Logo

Introducing Structon: Random-Access Binary Encoding for JavaScript

Deserializing entire records to read one field is a bottleneck at scale. Structon stores objects in a binary format where any field is reachable by byte offset, with lazy getters that never allocate until you access a property. It's the encoding Harper has used internally for years, now a standalone package.
JavaScript
Tutorial
Deserializing entire records to read one field is a bottleneck at scale. Structon stores objects in a binary format where any field is reachable by byte offset, with lazy getters that never allocate until you access a property. It's the encoding Harper has used internally for years, now a standalone package.
Person with very short blonde hair wearing a light gray button‑up shirt, standing with arms crossed and smiling outdoors with foliage behind.
Kris Zyp
SVP of Engineering
Tutorial

Introducing Structon: Random-Access Binary Encoding for JavaScript

Deserializing entire records to read one field is a bottleneck at scale. Structon stores objects in a binary format where any field is reachable by byte offset, with lazy getters that never allocate until you access a property. It's the encoding Harper has used internally for years, now a standalone package.
Kris Zyp
Jun 2026
Tutorial

Introducing Structon: Random-Access Binary Encoding for JavaScript

Deserializing entire records to read one field is a bottleneck at scale. Structon stores objects in a binary format where any field is reachable by byte offset, with lazy getters that never allocate until you access a property. It's the encoding Harper has used internally for years, now a standalone package.
Kris Zyp
Tutorial

Introducing Structon: Random-Access Binary Encoding for JavaScript

Deserializing entire records to read one field is a bottleneck at scale. Structon stores objects in a binary format where any field is reachable by byte offset, with lazy getters that never allocate until you access a property. It's the encoding Harper has used internally for years, now a standalone package.
Kris Zyp