Compared to other decentralized databases

Our vision

The next four part are the key points that the development of the database for Web3 should focus on.
Today DB3 is more interested in making sure of transparency.
four stages of web3 database

Differs from other decentralized databases

Text
DB3
Ceramic
WeaveDB
Polybase
The Graph
Brief intro
a fully decentralized database network that developers can use sql to access and use DVM to develop smart contract on it.
Peer-to-peer databases database protocol that maintain streams base on IPFS
NoSQL database designed for retrieval the long-term data storage in Arweave
a decentralized firesbase
a protocol that using Graphql to query the data on ethereum and IPFS
DB Type
SQL
Key-Value Store
No-sql, document-oriented
document
Models
Account based data permission model, account to data
Account to single JSON object (Data Models)
the disposal (like a delegate or redirect) private key to the JSON object
Pubkey to the collections (conceptually similar to a database table)
Storage
shard storage chain base on decentralized network
TileDocument streams
document on the Arweave permanent storage
shard storage chain base on decentralized network
Indexing
setting the indexes in your data tables
None
indexes the stored data with single and multi-field indexes
multi-field indexes
Queries
JS Library Method
FPJSON and the JSON-like simple query APIs
query and fetch data change in react
Clients
HTTP Client, ModelManager,DataStore
web console, light client
Accounts
secp256k1 for EVM-based accounts
3ID as default
EVM-based accounts
Authentication
use the delegate account’s private key to sign every trx and data exchange
All-or-nothing permissions
functions and also combined with JSONLogic to build access control.
sign every operation using publicKey
UX
Specific Ceramic sign-in popups
web console and wallet based sign-in
Specific sign-in popups
Incentive mechanism
POS Network Self-Operating Tokens
None
arweave‘ s incentive mechanism
Network Self-Operating Tokens