Insights and Updates

Read the HarperDB teams’ thoughts on database technology topics such as SQL, NOSQL, Edge Computing, IoT, Industry 4.0, and more

Using HarperDB to Integrate Insurance Data

October 16, 2018
*e2Value UI powered by the HarperDB database (Street addresses blurred out for privacy)
You never know where you’re going to meet your next business connection. Fred (COO) and Stephen (CEO) met on an airplane years ago and founded HarperDB years later. This year, we met Todd Rissel, CEO of e2Value , at the IoTBuild conference in Santa Clara, CA. A little less of a chance encounter than a plane, but an introduction nonetheless. 
Read More

HarperDB’s Exploded Data Model

June 20, 2018

If you’ve looked around our website, talked to us at a trade show, or read an article about us, you’ve probably heard about our exploded data model. This is the keystone of HarperDB’s innovative database solution. Our patent-pending exploded data model is the reason we are fully-indexed with no data duplication, it’s why we can support full SQL and NoSQL within a single model, and it’s the basis for even more innovative features to come. I know, I know, that’s all well and good, but how does it work?

Read More

Is HarperDB a Document Store?

May 01, 2018

No is the short answer.  Why does this matter?  Often when talking to the community I find that people are trying to understand where HarperDB fits in the database ecosystem.  Most people are primarily familiar with NoSQL databases, RDBMS, graph databases, and time-series databases.   A lot of people use the term Document Store and NoSQL database interchangeably.  In technology it is a pretty common practice to relate new and emerging technology to existing technology that is understood.  While HarperDB shares a lot of similarities with traditional NoSQL databases, it is not in fact a Document Store.  I thought it might be helpful to explain this further for folks trying to understand HarperDB at a deeper level.  

Read More

Dynamic Schema: The HarperDB Way

March 12, 2018

How can you possibly have a dynamic schema? Isn’t the purpose of a schema to provide structure to your data? Well, yes, schemas exist to contain objects and define structure. But what happens if I know my data will continue to evolve, as it tends to do? Should you have to constantly rely on developers and DBAs to develop the schema updates, test them, then deploy? To put it simply, no, that’s a lot of overhead. The HarperDB Dynamic Schema adapts to your ever-changing data, all while providing the ability to access that data however you need.

Read More