📚 ComposeDB on Ceramic

Is a decentralized, composable graph database built on IPFS
Unlocks app composability by redesigning the database for Web3
Introduces **data models—**modular DB schema that enable apps to share data. All Ceramic Streams used by ComposeDB are either Data Model Streams (the schemas) or Model Instance Streams (instances of a particular schema).
Data Models could include building blocks like:

🪪 identity, credentials & reputation

📎 DAO governance & tasks

🎙 social content & activity

🧰 Major Upgrades

Indexing: Data Models on your node stay in sync with global state
A new CLI for ComposeDB and a GraphQL client for querying model data
Open source data models, CLI, and GraphQL Client within js-composedb
Graph Relations supporting use cases like indicating followers/following between accounts and enabling ties between models (e.g. liking or commenting related to a social post)

🔮 Changes Beyond ComposeDB on Ceramic

Ceramic Streams, the mutable layer on top of IPFS, remains the same within js-ceramic (except for the new Model and Model Instance Document streamtypes)
Improved scalability: with multiple anchor workers powering CAS (Ceramic Anchor Service)
The Accounts repo js-did supports the new default DID method did:pkh
- did:pkh is a secure and user-friendly way to sign-in with your wallet to an app
- Pairs with the did-session package to allow devs to act on their users' behalf during a session, without having to sign every data transaction
- Support for Ethereum accounts currently, with Solana and more chains coming soon

<aside> 🐉 Here be dragons! While this has been tested for over 3 months, you’re likely to encounter bugs. ComposeDB is deployed on our Clay testnet not mainnet yet — there is no data permanence. We highly advise against using ComposeDB in production at this early stage.

</aside>

Getting Started With ComposeDB on Ceramic

These guides are meant to:

🔍 Preview how ComposeDB works