As the Internet of Things matures we continue to see design patterns come and go, with some evolving and some disappearing. The time has come- Store and Forward needs to go. This paradigm served as an initial step in shifting to the edge, but it should not survive. In this blog I’ll introduce the concepts of Store and Forward along with an explanation of its inferiority to other, more modern edge computing paradigms.
If you’ve made it to this blog you’ve probably heard the term“persistent” thrown around with ETL,and are curious about what they really mean together. Extract, Transform, Load(ETL) is the generic concept of taking data from one or more systems and placing it in another system, often in a different format. Persistence is just a fancy word for storing data. Simply put, persistent ETL isadding a storage mechanism to an ETL process. That pretty much covers the what, but the why is much more interesting…
*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.
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.