LF, a decentralized storage of replicated data

LF is a decentralized storage of replicated data in key / value format that is being developed by ZeroTier, that develops a virtual Ethernet switch that allows to combine hosts and virtual machines located in different providers in a virtual local area network, whose participants exchange data in P2P mode.

Previously, the LF code was available under the BSL license (Business Source License), which is not free due to discrimination against certain categories of users. The BSL license was proposed by the co-founders of MySQL as an alternative to the Open Core model. The essence of BSL is that the code for extended functionality is initially available for modification, but for some time it can be used free of charge only if additional conditions are met, to bypass what the purchase of a commercial license requires.

LF is a completely decentralized system and allows to implement a single data warehouse in key value format on an arbitrary number of nodes. All nodes keep data in sync and all changes are fully replicated across all nodes, plus all LF nodes are the same. The absence of separate nodes coordinating the work of the storage allows to get rid of a single point of failure and the presence of a complete copy of the data in each node eliminates the loss of information in case of failure or shutdown of the individual.

To connect a new node to the network, you do not need to obtain separate permissions; anyone can start their own node. The LF data model is based on a directed acyclic graph(DAG) that simplifies synchronization and enables different security and conflict resolution strategies.

Unlike distributed hash table (DHT) based systems, the IF architecture was originally designed for use in unreliable networks, where the constant availability of nodes is not guaranteed. LF applications include creating the most resilient storage systems that store relatively small amounts of mission-critical data that rarely change. For example, LF is suitable for keystores, certificates, credentials, configuration files, hashes, and domain names.

To protect against overload and abuse, a limitation of the intensity of operations is applied write to shared storage, implemented on the basis of a proof of work (proof of work), in order to save data, a member of the storage The network must perform a certain task, which is easily verified, but requires large computational resources (similar to organize the expansion of systems based on blockchain and CRDT). The calculated values ​​are also used as an indicator for conflict resolution.

Alternatively, a certificate authority can be launched on the network to issue cryptographic certificates to participants that give the right to add entries without confirmation of the work and give priority in the resolution of conflicts. By default, storage is available without restrictions to connect participants, but optionally, depending on the certificate system, fenced private storages can be created, in which only nodes certified by the network owner can become participants.

Of the main characteristics of LF, the following stand out:

  • Ease of deploying your storage and connecting to existing public storage networks.
  • The absence of a single point of failure and the ability to involve everyone in the maintenance of the store.
  • High speed access to all data and the ability to access the data left on your node, even after a network connectivity failure.
  • A universal security model that allows combining various conflict resolution mechanisms (local heuristics, weighting based on the work performed, taking into account the trust level of other nodes, certificates).
  • Flexible API for querying data, allowing you to specify multiple nested keys or ranges of values. Ability to bind multiple values ​​to a key.
  • All data is stored encrypted, including keys, and verified. The system can be used to organize confidential data storage on untrusted nodes. Records, whose keys are not known, cannot be determined by brute force method (without knowing the key, it is impossible to obtain the data associated with it).
  • Among the limitations, the focus is on storing small data that rarely changes, the absence of locks and guaranteed data consistency, high CPU, memory, disk space and bandwidth requirements, and a constant increase in storage size. over time.

Finally, if you are interested in knowing more about it, you can consult the details In the following link.


Be the first to comment

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.