HarperDB Benchmark | HarperDB vs. Macrometa

Summary

For enterprise use cases at scale, HarperDB is by far a superior platform – providing developers with a high-performance containerized application delivery platform that meets requirements now and in the future.‍

"38% of devs say they are more likely to use a database that is on-prem and cloud."
- 451 Research

‍

Overview

Based on functional requirements, the ideal use cases for HarperDB and Macrometa may look nearly identical. But those are only the functional requirements. Once you consider the real-world impact of developer experience, throughput, latency, scalability, and TCO (non-functional requirements), the use case overlap evaporates.
‍
HarperDB handles 140,000 transactions per second (TPS) per node and scales linearly. Macrometa can handle 300 TPS globally across their entire 170 node network. In comparison, HarperDB on 170 nodes can handle 23,800,000 TPS or 79,300x the transaction volume of Macrometa. Such high performance on a single node means companies need significantly fewer servers, saving enterprises millions per year.

‍HarperDB is a future-proof investment. With HarperDB, you have the flexibility of a fully managed serverless FaaS architecture with the flexibility to deploy anywhere. Macrometa restricts data storage and computing to the cloud, limiting your technology runway. In a world moving towards a Web3 paradigm, today’s technology investments must be able to adapt. HarperDB’s platform allows enterprises to shift seamlessly between the cloud, edge, and decentralized peer-to-peer networks, giving you a runway to the future.

‍Keep developers happy and develop solutions in less time. Macrometa is particular. They require developers to learn their proprietary hybrid SQL-Java language to write queries. They need developers to rework their CI/CD pipeline, adjust their version tools, and work around limitations on NPM packages.

On the other hand, HarperDB simplifies existing workflows. With HarperDB, you get to keep using your existing CI/CD pipeline, GitHub actions, NPM packages, IDE, and more. Oh, and want to write a query? Just use good old fashion SQL or NoSQL, you choose.