Christmas break Bluzelle DB development update

Neeraj Murarka
The Blueprint by Bluzelle
2 min readDec 26, 2017

--

Bluzelle’s team has been hard at work in 2017 working on the Bluzelle database. The database comes in many parts including client software, GUI software, and the all-important farming daemon, which is software that powers each node in the network.

Bluzelle would like to foster a pattern of updates to Github on the devel and master branches, as frequently as practical, so that members of the community can participate actively. This includes community members familiarizing themselves with the software, testing it out, community planning around 3rd party modules and plugins that would use Bluzelle, pull requests, and feedback from the community.

It is vital for Bluzelle that the community engages this way to ensure the product has solid and regular optics on what database consumers and farmers need and want. Bluzelle will be releasing code regularly even prior to it being feature complete. This point should be diligently noted when using our software.

Prior to the Christmas break, the team published code to Github that enables the sharing of data between a leader node and a series of subordinate (follower) nodes in a single swarm. The features of this codebase are limited but allow the user to run multiple instances of the daemon on a single machine, and to see the different daemons talking to each other and propagating the values and deltas handed down by the leader node. Only creates and reads work, with creates being issued to the leader and reads working on all nodes.

To try this code out, follow the README.md file found at the devel branch:

Community members should always look at the devel branch for the latest code, and consider it very untested and pre-alpha, as well as feature incomplete, unless otherwise stated.

More stable codebases will be released to master and announced separately.

We immediately welcome and encourage community members and especially software developers to clone the code and give it a spin! We also ask for all forms of constructive feedback, irrespective of where we are in the timeline. This includes feedback on the code as well as documentation.

Happy Holidays!

--

--