This article was first published on The Blueprint by Bluzelle - Medium
The Bluzelle team has been hard at work in the past sprints. In this blog post, I am glad to share with you:
- Recent updates on development sprint #41 & #42
- The launch of developer bounty program
While our full version is still in private mode for selected partners and customers, the public can still access our test version with the latest features.
The latest added features are as follow:
- New CreateDB size constraint functionality. In the test version, anyone can create a database and we now support an optional parameter to specify the maximum size (in bytes) of your database. If you leave this parameter out, there is no maximum enforced.
- A random eviction policy on a per database (UUID) basis. For databases that have specified a maximum size when created with CreateDB, when that database reaches its maximum and an attempt is made to exceed that maximum (ie: with a Create or Update), existing data already in the database will be evicted (deleted), on the basis of randomly choosing a minimum number of key-value pairs to remove until enough space is available.
- Create and Update now allow for a TTL value to determine expiry time, on a per key-value-pair basis. An important aspect of building an application that is intended to run on the Bluzelle DB is resource management. Specifically, ensuring your application does not exceed the maximum size of the database you are paying for. A key means to do this is to keep tight TTL (total time to live) settings on every key-value-pair you store. Now you are allowed to specify the optional TTL when you create a key-value-pair. If you do not specify it, the key-value-pair lives forever. If you specify it (in seconds), when that time elapses, the key-value-pair ...
To keep reading, please go to the original article at:
The Blueprint by Bluzelle - Medium