We’ve all been working hard here at HarperDB to bring you the new and improved HarperDB 2.0. One of the main features that received a makeover was our solution for enhancing distributed computing, and more specifically, clustering. The new version has improvements across the board with performance, reliability and scalability. In this blog I’m going to introduce the concept of clustering and how it works with HarperDB.
At HarperDB, we’re working to build the best distributed database solution from the edge to the cloud. As a software developer on the team, I spend most of my time thinking about how to increase the stability and speed of our codebase - ideally, any work I’m doing achieves both of these priorities.
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!
During a recent trip to NodeJS Interactive in Vancouver last October, Zach(Chief Product Officer) and Eli(Principal Engineer) spoke to multiple people who suggested they look into Node-RED, especially since they built an IoT database. The guys came back home, did some quick research, thought“this looks pretty cool,” then threw it on the backlog…where it sat for a while. Whoops. In the last few months we finally got around to diving into Node-RED and, wow, is it powerful!