Migrating to ComposeDB on Ceramic

If you are an existing Ceramic developer, you might be wondering how you can migrate or upgrade your application to ComposeDB. We are not shipping any migration tools during the early preview of this release, but we will look into it depending on your feedback.

Below, you can find guidelines on what you should keep in mind if you have an existing application built on Ceramic and would like to use ComposeDB.

ComposeDB introduces a new method of querying and mutating data on Ceramic. Therefore, if you’re migrating from Self.id or from glazed , you’ll need to:

Create a separate composite for each of your apps, using existing models when possible and/or creating new composites if necessary
Ensure that Ceramic nodes, which connect to each of your apps, are indexing all the data models from the corresponding app’s composite. You do this by updating the node’s config files and setting environment variables (shown earlier in the Getting Started guide).
In the codebase of each app you’ll need to:
- Replace uses of SelfID with proper uses of ComposeClient, according to the documentation (if you’re migrating from Self.id)
- Replace uses of TileLoader with proper uses of ComposeClient, according to the documentation (if you’re migrating from glazed)
Contact us on the forum if you have any issues with the steps above
Additionally, you may decide to use a popular GraphQL tool, e.g. apollo or graph-relay, according to our docs

The Future of Other Tools in Ceramic’s Ecosystem

Here are the plans for other tool kits currently available in Ceramic’s ecosystem.

3ID Connect

Self.ID SDK

Self.ID Website

Glaze Packages

<aside> 🎤 We want to hear your feedback! Please take this 5-minute survey or chat with us on the forum.

</aside>