Click Below to Get the Code

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

HarperDB 4.4 Unleashes 50% Faster Replication & Sharding for Scalable Apps

HarperDB 4.4 delivers a breakthrough in performance and scalability. Get 50% faster replicated writes and leverage sharding for massive data with this distributed systems platform. Ideal for large-scale retail, gaming & media applications. Learn more!
Announcement
News
Announcement

HarperDB 4.4 Unleashes 50% Faster Replication & Sharding for Scalable Apps

Harper
at Harper
October 14, 2024
Harper
at Harper
October 14, 2024
Harper
at Harper
October 14, 2024
October 14, 2024
HarperDB 4.4 delivers a breakthrough in performance and scalability. Get 50% faster replicated writes and leverage sharding for massive data with this distributed systems platform. Ideal for large-scale retail, gaming & media applications. Learn more!
Harper

Denver, CO – October 15, 2024 – HarperDB, a Distributed Systems Platform, announces general availability of HarperDB 4.4. The new release delivers a 50% increase in replicated write performance, as well as support for sharding, enabling engineers to take advantage of the platform’s unlimited horizontal scale. 

“Performance gains were made possible by consolidating a previously standalone replication function with the existing transaction log to create a single, more efficient replication system,” explains Kris Zyp, VP of Engineering at HarperDB. “The updated replication system, codenamed ‘Plexus,’ is more performant, efficient, secure, and reliable than previous approaches.”

HarperDB 4.4 also includes support for sharding, enabling efficient storage for massive data volumes across customers’ globally distributed applications. Sharding leverages HarperDB’s new, high-performance replication technology, enabling unlimited horizontal scale for reads and deep system redundancy. 

With the performance gains introduced by these two key features, developers can now utilize HarperDB for large-scale IoT, gaming, and social media use cases that require high write throughput.

Also in this release:

  • Computed Properties allow developers to define properties to be computed from other properties, enabling easy definition and querying of data that is not advantageous to store, like discount prices, shipping costs, and gaming stats. 
  • Custom Indexes can now be based on computed properties, enabling unlimited possibilities for indexing, including composite, full-text, and vector indexing.
  • Replicated Operations make for easy management of large distributed clusters by enabling restarts and component management operations to be “replicated,” reducing the DevOps workload. 
  • Dynamic Certificate Management allows certificates to be added, replaced, and deleted without restarting HarperDB, streamlining security management.
  • For a complete list of updates, read the release note.

About HarperDB

HarperDB eliminates the complexity typically synonymous with distributed services by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and application components into a single distributed technology. When clustered and geo-distributed, HarperDB nodes instantly synchronize data to deliver a horizontally scalable Service Fabric, ensuring low-latency in-region responses for clients worldwide. In addition to massive cost savings at scale, HarperDB's REST, GraphQL, and real-time interfaces make light work of servicing frontend requirements. Visit www.harperdb.io for more information.

Media Contact:

Aleks Haugom, GTM Lead

hello@harperdb.io 

Denver, CO – October 15, 2024 – HarperDB, a Distributed Systems Platform, announces general availability of HarperDB 4.4. The new release delivers a 50% increase in replicated write performance, as well as support for sharding, enabling engineers to take advantage of the platform’s unlimited horizontal scale. 

“Performance gains were made possible by consolidating a previously standalone replication function with the existing transaction log to create a single, more efficient replication system,” explains Kris Zyp, VP of Engineering at HarperDB. “The updated replication system, codenamed ‘Plexus,’ is more performant, efficient, secure, and reliable than previous approaches.”

HarperDB 4.4 also includes support for sharding, enabling efficient storage for massive data volumes across customers’ globally distributed applications. Sharding leverages HarperDB’s new, high-performance replication technology, enabling unlimited horizontal scale for reads and deep system redundancy. 

With the performance gains introduced by these two key features, developers can now utilize HarperDB for large-scale IoT, gaming, and social media use cases that require high write throughput.

Also in this release:

  • Computed Properties allow developers to define properties to be computed from other properties, enabling easy definition and querying of data that is not advantageous to store, like discount prices, shipping costs, and gaming stats. 
  • Custom Indexes can now be based on computed properties, enabling unlimited possibilities for indexing, including composite, full-text, and vector indexing.
  • Replicated Operations make for easy management of large distributed clusters by enabling restarts and component management operations to be “replicated,” reducing the DevOps workload. 
  • Dynamic Certificate Management allows certificates to be added, replaced, and deleted without restarting HarperDB, streamlining security management.
  • For a complete list of updates, read the release note.

About HarperDB

HarperDB eliminates the complexity typically synonymous with distributed services by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and application components into a single distributed technology. When clustered and geo-distributed, HarperDB nodes instantly synchronize data to deliver a horizontally scalable Service Fabric, ensuring low-latency in-region responses for clients worldwide. In addition to massive cost savings at scale, HarperDB's REST, GraphQL, and real-time interfaces make light work of servicing frontend requirements. Visit www.harperdb.io for more information.

Media Contact:

Aleks Haugom, GTM Lead

hello@harperdb.io 

HarperDB 4.4 delivers a breakthrough in performance and scalability. Get 50% faster replicated writes and leverage sharding for massive data with this distributed systems platform. Ideal for large-scale retail, gaming & media applications. Learn more!

Download

White arrow pointing right
HarperDB 4.4 delivers a breakthrough in performance and scalability. Get 50% faster replicated writes and leverage sharding for massive data with this distributed systems platform. Ideal for large-scale retail, gaming & media applications. Learn more!

Download

White arrow pointing right
HarperDB 4.4 delivers a breakthrough in performance and scalability. Get 50% faster replicated writes and leverage sharding for massive data with this distributed systems platform. Ideal for large-scale retail, gaming & media applications. Learn more!

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