- IceFireDB - Decentralized Database Infrastructure
- Decentralized database engine
- Documentation center
- Project composition
- System Design
- Quick Start
- Performance
- Project direction
- Thanks support
Based on cutting-edge computer science, the IceFireDB project integrates new ideas and research in the fields of message passing, event instruction processing, data consistency and replication, decentralized network, reliable data storage, high-performance network framework, etc.The team of researchers and engineers at IceFireDB combines the cutting-edge ideas from distributed systems and concurrent databases. These ideas combine collision-free replication data types (CRDT) and decentralized appendix-only logs, which can be used to simulate the variable sharing state between peers in P2P applications to create a new data infrastructure with high security, high performance and low latency.
The core of IceFireDB architecture is geographically distributed event source and decentralized Log source, with log-level CRDT replication.In order to realize the consistency of replication, IceFireDB provides a stable decentralized networking model, which allows the combination of public networks among different sites. Multiple IceFireDB nodes can be run inside each site, and RAFT network can be formed between nodes, which ensures the data consistency and stable storage within the same site.
IceFireDB is a database built for web3 and web2. The core mission of the project is to help applications quickly achieve decentralization and data immutability. At present, the storage layer supports various storage methods such as disk, OSS, and IPFS. The protocol layer currently supports SQL and RESP protocols, and will support GraphQL protocols in the future.A blockchain fusion layer based on immutable transparent logs and Ethereum is under construction to support integration with higher-level decentralized computing platforms and applications as well as identity, financial assets, intellectual property and sidechain protocols. IceFireDB strives to fill the gap of the decentralized stack, making the data ecology of web3 applications more complete, and making it easier for web2 applications to achieve decentralization and data immutability.
| Feature | Status |
|---|---|
| High performance | Ongoing optimization |
| Support LSM disk, OSS, IPFS underlying storage | Implemented |
| Distributed consistency (support Raft, p2p-crdt, IPFS-log modes) | Implemented |
| Based on IPFS decentralized storage, build a persistent data distributed storage layer | Beta version |
| Support P2P automatic networking, build decentralized NoSQL and SQL data synchronization | Beta version |
| Support decentralized consistent KV storage engine (icefiredb-crdt-kv and icefiredb-ipfs-log) | Beta version |
| Support AI vector database storage and instructions | In progress |
| Integrate with NATS for high-performance decentralized networking | In progress |
| Support KV and SQL immutable storage engine (combined with immudb) | In progress |
| Supports scalable, auditable, and high-performance tamper-resistant logging (combined with qed) | Planned |
| Build an immutable transparent log witness layer between Web2 and Web3, build a data hot and cold hybrid structure, and an immutable data bridge layer (inspired by Google Trillian-Witness and IPLD) | Planned |
| Support KV metadata layer and mixed storage structure of hot and cold | Planned |
| More advanced cache implementation, faster LSM persistent storage (Source) | Planned |
Documentation center : https://www.icefiredb.xyz/icefiredb_docs
IceFireDB-SQLite database is a decentralized SQLite database. Provide a convenient mechanism to build a global distributed database system. Support users to write data to IceFireDB-SQLite using MySQL protocol. IceFireDB-SQLite stores the data in the SQLite database and synchronizes the data among the nodes in the P2P automatic network.
IceFireDB-SQLProxy is a decentralized SQL database networking system that helps web2 traditional SQL database data decentralization. Provide a convenient mechanism to build a globally distributed storage system with automatic networking. Commands are automatically synchronized between IceFireDB-SQLProxy in the network, and each IceFireDB-SQLProxy writes data to MySQL storage.
Decentralized networking through IceFireDB-SQLProxy provides web2 program read and write support for SQL, enabling decentralized data synchronization for MySQL database read and write scenarios commonly used in web2 applications.
IceFireDB-Redis-proxy database proxy adds decentralization wings to traditional redis databases. Provide a convenient mechanism to build a globally distributed storage system with automatic networking. The instructions are automatically synchronized between the networked redis agents, and the redis agent writes data to the cluster or single-point redis storage. Through the decentralized middleware network proxy, decentralized data synchronization can be enabled for the Redis database commonly used in web2 applications.
IceFireDB-PubSub is a high performance, high availability and decentralized subscription system.It can seamlessly migrate web2 applications using redis publish and subscribe into a decentralized p2p subscription network.
It supports distributed raft disk Redis database mode in web2 mode, and also supports decentralized IPFS storage mode.
| Strings | Hashes | Lists | Sets | Sorted Sets |
|---|---|---|---|---|
| APPEND | HSET | RPUSH | SADD | ZADD |
| BITCOUNT | HGET | LPOP | SCARD | ZCARD |
| BITOP | HDEL | LINDEX | SDIFF | ZCOUNT |
| BITPOS | HEXISTS | LPUSH | SDIFFSTORE | ZREM |
| DECR | HGETALL | RPOP | SINTER | ZCLEAR |
| DECRBY | HINCRBY | LRANGE | SINTERSTORE | ZRANK |
| DEL | HKEYS | LSET | SISMEMBER | ZRANGE |
| EXISTS | HLEN | LLEN | SMEMBERS | ZREVRANGE |
| GET | HMGET | RPOPLPUSH | SREM | ZSCORE |
| GETBIT | HMSET | LCLEAR | SUNION | ZINCRBY |
| SETBIT | HSETEX | LCLEAR | SUNIONSTORE | ZREVRANK |
| GETRANGE | HSTRLEN | LMCLEAR | SCLEAR | ZRANGEBYSCORE |
| GETSET | HVALS | LEXPIRE | SMCLEAR | ZREVRANGEBYSCORE |
| INCR | HCLEAR | LEXPIREAT | SEXPIRE | ZREMRANGEBYSCORE |
| EXISTS | HMCLEAR | LKEYEXISTS | SEXPIRE | ZREMRANGEBYRANK |
| GET | HEXPIRE | LTRIM | SEXPIREAT | |
| GETBIT | HEXPIREAT | LTTL | STTL | |
| SETBIT | HKEYEXIST | SPERSIST | ||
| GETRANGE | HTTL | SKEYEXISTS | ||
| GETSET | ||||
| INCRBY | ||||
| GET | ||||
| MGET | ||||
| MSET | ||||
| SET | ||||
| SETEX | ||||
| SETEXAT | ||||
| SETRANGE | ||||
| EXPIRE | ||||
| EXPIREAT | ||||
| TTL |
IceFireDB refines and implements the following important system components.
| System components | describe | technology used |
|---|---|---|
| Network layer | 1. RAFT guarantees data consistency within a single availability zone. 2. P2P network construction decentralized database communication. 3. NATS is a new network layer being built. |
P2P、RAFT、NATS |
| Storage layer | Many types of storage are currently supported. Under the codec computing layer, we abstract the KV storage driver layer, which is compatible with different storage engines of web2 and web3. | goleveldb、badger、IPFS、CRDT、IPFS-LOG、OSS |
| Protocol layer | Based on the codec layer, we have built a protocol layer. A good communication protocol allows more applications to easily access the IceFireDB data network. Currently, we support the Redis-RESP NoSQL protocol and the MySQL protocol. | RESP、SQL |
| Codec layer | The codec layer is the core of our system. For NoSQL scenarios, any data type will be abstracted into a KV storage model. With the flexible coding layer, we can build rich data operation structures and instructions, such as hash, sets, strings, etc. | KV、Strings、Hashes、Lists、Sorted Sets、Sets、SQL、PubSub |
https://www.icefiredb.xyz/icefiredb_docs/icefiredb/icefiredb-nosql/quick_start/
leveldb driver
corerman@ubuntu:~/DATA/ICODE/GoLang/IceFireDB$ redis-benchmark -h 127.0.0.1 -p 11001 -n 10000000 -t set,get -c 512 -P 512 -q
SET: 253232.12 requests per second
GET: 2130875.50 requests per secondIceFireDB originated from the distributed NoSQL database in the web2 scenario. We will continue to support the web2 distributed NoSQL database, while investing more energy in the direction of web3 and web2 decentralized databases. We are very grateful to our community partners for their continued interest, the community has been our driving force.
I stood on the shoulders of giants and did only simple things. Thank you for your attention.
- https://github.com/tidwall/uhaha
- https://github.com/syndtr/goleveldb
- https://github.com/dgraph-io/ristretto
- https://github.com/ledisdb/ledisdb
- https://github.com/dgraph-io/badger
- https://github.com/ipfs/ipfs
- https://github.com/libp2p
 Protocol Labs |
 Filecoin |
 FVM |
 libp2p |
License
Disclaimers
When you use this software, you have agreed and stated that the author, maintainer and contributor of this software are not responsible for any risks, costs or problems you encounter. If you find a software defect or BUG, please submit a patch to help improve it!