Enter the Fluence
Hello and welcome to Fluence!
This document is the best way to learn about what Fluence is and, depending on what you want to do, where to go next. It will be constantly updated with new links and content.
State of the dapps
In the future, a large amount of data is going to be on-chain and in other decentralized storages. Chaining data gives advantages that were not easily obtainable before: transparency for contributing parties, audit trails and social consensus.
While building applications on top of the decentralized data with comprehensive business logic as well as being able to provide a smooth user experience in a browser or on mobile, consider this:
- Reading on-chain data is hard. Full nodes are not incentivized to provide data or process large numbers of read requests; therefore, private API providers emerged and now control the network. App developers are forced to trust these centralized intermediaries to work with blockchain data.
- Processing on-chain data is even harder. In order to perform computation on top of historical blockchain data, a developer usually needs to find a way to index the data first. Building a custom index for blockchain is not a trivial task, which requires resources and time. Moreover, the code that processes on-chain data usually sits off-chain which makes the whole endeavour pretty centralized and therefore, defeats the purpose.
In the traditional stack, these problems did not exist since the tasks have been managed by a combination of a database and a backend. Roughly speaking, they were either optimized for both “reads” and “writes” or had a complex architecture where one part was used for “writes” and another for “reads”.
In the future, a large amount of data is going to be on-chain and in other decentralized storages.
Blockchains today are mostly being optimized for “writes” (i.e. appending new data and verifying its validity) which means increasing the number of transactions per second but they usually miss the “read” part. They serve as (relatively slow) databases and minimal backends (using smart contracts).
To address this, the “read model” can be decoupled from blockchains to another self-sufficient network. It offers both more flexibility and the ability to build real-time applications with world-class user experiences.
Read model for the decentralized stack
Fluence is the platform for accessing, querying, and processing data from various decentralized sources, including blockchains and file storages.
Fluence creates an independent network with its own decentralized consensus for each query, security model and crypto-economics design. This network is optimized for retrieving and processing data from decentralized sources without sacrificing the security and performance. Databases, query languages and arbitrary algorithms can be created and deployed to the Fluence network and can run completely decentralized on the Fluence virtual machine.
Such an independent way unlocks lots of new use cases that previously required compromises like relying on a central party or performance limitations. Developers will be able to move from solving infrastructural challenges to actually building applications.