Performance

First of all, we’re not claiming that databases like Bluzelle will have performance that supersedes the speed of a local dedicated database on the same machine, or same local area network as the client using the database.

Bluzelle’s performance is defined in terms of consistency and how its design ensures that performance is always maintained, either when the network is having heavy load in general, or when the client itself has a massive amount of data that needs performance hand in hand with scalability.

Within a swarm, there are potentially thousands or millions of nodes, any of which can serve a database request. Bluzelle will intelligently (using AI-inspired search techniques) figure out which of those nodes are most appropriate to serve the request, based on many factors including distance from the nodes to the client making the request.

In fact, within that swarm, multiple nodes can be commissioned to service that request in parallel, where they all compete to respond first. This level of parallelism gives the best possible performance amongst the participating nodes. As the load increases, the number of nodes that are commissioned to parallelize tasks adjusts automatically to ensure that performance levels are maintained. These nodes are strategically chosen within the swarm to match the specifics about the client.

Bluzelle also uses 2D partitioning to optimize with greater granularity how data is stored on swarms. For instance, more important fields can be stored separately and with higher performance standards than lesser important fields.

Edge caching is an optional feature that allows Bluzelle to cache highly-requested data closer to where the client is, ensuring that performance can be fine tuned and increased, whenever needed.

In general, Bluzelle’s swarming model with a large collection of nodes within each swarm and its various service levels introduces a responsive level of granularity that ensures that performance is kept consistent and adaptive to whatever demands are made of the database.

Reliability

The swarming model takes some of the concepts of Blockchain and applies them to swarms. More specifically, instead of having every piece of data replicated everywhere, data is intelligently broken up (sharded) into swarms, and within each swarm, every node replicates all the data on that swarm.

This model of partial replication ensures that data within the swarm is always available, even if one or many nodes in the swarm fail. In fact, even in the statistically unlikely event that half the nodes in a swarm fail, the data will still be intact and available. Short of a global catastrophe where the entire Internet fails, any data stored on Bluzelle will be available with an effective 100% guarantee.

Bluzelle’s design has absolutely no dependency on any form of centralized computing, whether it is nodes on a cloud or consortiums of machines. All data is stored on nodes in a non-deterministic way that ensures hacking is difficult while performance, scalability, and availability is maintained. This level of reliability cannot be attained in any practical means by existing traditional database products.

Scalability

Bluzelle’s scalability ties strongly into its performance, where the key requirement behind scalability is to ensure that performance levels are kept consistent even as the amount of data being stored/read and the frequency of these operations increases or decreases.

More specifically, when there is a gradual or sudden increase in the amount of data being stored, Bluzelle’s design automatically distributes the data uniformly across the entire network of swarms, ensuring that subsequent attempts to read or update or delete that data are also uniformly distributed and meeting the requirement for performance consistency. Increased transactions also automatically get parallelized to the multiple nodes in a given swarm, all of which are qualified to service requests for the swarm’s data. This means that increases in demand for that data are also automatically and uniformly distributed, providing a consistent performance level.

Bluzelle does not require the user to pre-emptively purchase and spin up extra servers in anticipation of increased data storage and transfer requirements. Bluzelle is reactive instead of requiring the user to be proactive, and therefore provides the on-demand scalability needed to ensure that performance requirements are met with the consistency, granularity, and within the schedule that the customer requires.

Want to learn more and get first access to the white paper which explains this in more detail? Join our Telegram group to engage directly with our team.