HarperDB was Designed with App Developers in Mind

Lightweight, easy to use, and powerful. Worry about your app, let HarperDB worry about your database.

  • Harper-HowItWorks-step1-fixedFINAL.png

    Simple REST API

    Write to a schema-less single model with either JSON or SQL using HarperDB’s single model architecture and easy-to-use REST API.

  • Harper-HowItWorks-step2.png

    Exploded Data Model

    Instead of storing this data as columns and rows or a document store, HarperDB explodes the data into individual indices.

  • Harper-HowItWorks-step3.png

    Natively Indexed

    Each attribute is stored separately, allowing for HarperDB to be fully indexed without creating additional overhead.

  • Harper-HowItWorks-step4-revised-1.png

    SQL and NoSQL

    You can then query or search HarperDB using SQL or noSQL on any column. Using joins and multiple conditions and operators, HarperDB coalesces these indices back into a single object and returns the results in JSON or column row format.

Simplicity Without Sacrifice

With code examples in Go, Node, and PHP it is easy to get started with HarperDB. Simple copy and paste and you are good to go.  


Database as a Microservice

Interfacing with HarperDB is done through a simple to use REST API. HarperDB has a single end point with a consistent JSON object model that allows you to simply and explicitly interact with your data.

NoSQL and SQL Capabilities Natively, In Real-Time

HarperDB offers full NoSQL CRUD with features that are unique to HarperDB like joins, advanced math, and multiple conditions. HarperDB offers full CRUD operations via SQL like any traditional RDBMS which is intended to accommodate application and BI use cases. This allows ingestion of data via standard SQL INSERT & UPDATE as well as offering complex SQL queries with no performance impact on unstructured data. Joins, multiple operators, and multiple conditions are possible in sub-second time.

Fully-Indexed Database

While any product can be fully indexed, HarperDB is fully indexed without utilizing RAM or increasing the storage footprint. No configuration is required. This allows HarperDB to have equally fast performance on searching any attribute in the database without replicating data or utilizing expensive RAM.

Single-Model

Most products that provide both NoSQL and SQL capability do this using a concept called multi-model. Multi-model either duplicates your data or it utilizes significant amounts of RAM to do transformations in memory. This is expensive from a capital resource perspective. HarperDB’s single model means there is no transformation of data required and as a result, significant savings on storage and RAM.   

Schema-less

Most products that can provide full ANSI SQL capability with joins and multi conditions require schema management. This means tables, columns, data types, & indices must be defined, and significant configuration is required which often slows down integration. It also means these solutions have difficulty ingesting unstructured data as that data can change from insert to insert. HarperDB being Schema-less means that it is flexible enough to ingest unstructured data while at the same time providing complex SQL capability.

Learn How HarperDB Works

On Wednesday, November 15th at 11 am MT our engineering team will do a Technology Deep Dive and Q&A for our first HarperDB Webinar.

Join Our Webinar