Bluzelle Development Update (Sprint #37)

Completed features, feature demo and recent marketing activities.

Bluzelle
The Blueprint by Bluzelle
2 min readApr 26, 2019

--

Dear community,

This recaps what we have accomplished for Sprint #37 in the past 2 weeks. At the end of the summary, you can also watch a demo of one of the features accomplished in this sprint .

Sprint #37 Recap

  • Swarm in a box: As we have been adding more and more functionality to the Bluzelle swarm it has become increasingly necessary to deploy an end-to-end swarm within a single machine. Swarm in a box enables developers to test new code at their desk and will eventually allow for our test automation to run against test swarms.
  • Client C++ Library: This library will represent a multi-sprint effort to migrate from one-off implementations for various client driver libraries to a single base implementation in C++ that can be wrapped in multiple language bindings. The team completed an initial proof-of-concept on using a socket based IPC to asynchronously notify the client code in the native (Python, Ruby, JS) event loop. This is a big step forward.
  • Caching Specific Configuration: The team created a mechanism to ensure that K/V pairs within a given cache set can be appropriately evicted if the cache exceeds its max size. We are utilizing a random eviction policy and will continue to allow more granularity in the types of eviction policies that can be configured based on customer demand.

Sprint Highlight: Bootstrap different swarms of Bluzelle in a decentralized way via Ethereum

Marketing Activities

If you find this article useful, please give us some claps πŸ‘πŸ‘πŸ‘

Are you a developer? Try out Bluzelle via:

| Tech Documentation | Deploy to Heroku | Github | Gitter Community |

--

--