*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.
Recently, I was meeting with one of our partners and we were speaking in depth about HarperDB’s architecture and roadmap. During the conversation, what struck me as really interesting, was his focus on HarperDB’s stability and scalability. This was what excited him most about our product.
We have written a lot about the technical need to combine NoSQL and SQL solutions for handling big data workloads. That said, what are the business impacts of combining both NoSQL and SQL? When should I use an object model vs. a query model? What use cases require both? Today we thought we would look at best practices for each as we have given this a lot of thought in designing HarperDB.
Over the last several years multi-tiered database architectures have become increasingly popular. These architectures typically consist of multiple different database products and can be made up of NoSQL products, SQL products, In-Memory products, Object stores etc. A lot has been written about the benefits and the advantages.