One of the consistent themes that has surfaced when working with industrial clients is their reliance on high performance rotating machinery. Whether it’s steam turbines delivering electrical power or compressors in mid stream gas fields, these machines are the foundation for most heavy industries. If youconsider the combustion engine as a rotating machine as well, we are surrounded by equipment that has been engineered to spin large amounts of metal at significant frequencies for long periods of time. After spending some time with clients managing these machines, I am awed by the level of engineering required in these mechanical marvels of technology. I am also not surprised by the level of monitoring and maintenance required to keep these machines in action.
Hello world! My name is Sam and I am the newest member of the HarperDB Engineering Team.
While I may be relatively new, I have been following the company since they launched last year(I’ve known Stephen since college) and jumped at the opportunity to join this awesome team. I was and still am excited by the opportunity to help develop a database solution that is fully-indexed with no data duplication while also supporting full SQL and NoSQL within a single model. In Node.js, no less!
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.