<aside> <img src="/icons/code_gray.svg" alt="/icons/code_gray.svg" width="40px" /> TL;DR

• ComposeDB builders should benefit for OrbisDB services via a smooth migration
• ****A short-term vs long-term approach should be prioritized to managed Orbis other priorities
• Specific partners should access a white-glove service (e.g Passport)

</aside>

Proposal

OrbisDB will provide a migration plan and work on different path (simple vs advanced) to offer a clear pathforward for ComposeDB builders. We should have different approach based on organizations + volume of data, but also based on their technical set up (self-hosting? managed via Hirenodes?

Timeline:

To be discussed/confirmed

Current ComposeDB builders

| Project names | Project detail Are they building an SDK? a frontend app? a backend app? | ComposeDB Status Status of development, active or not? | Mainnet | Self-hosting *Where do they host their node? Hirenodes? If no: Details about their own server hosting* | ComposeDB Lib Do they use ComposeDB libraries for write (probably yes)? If yes: Mutation examples? If no: How do they write data? | Indexing Do they use ComposeDB GraphQL endpoint for reads (probably yes)? | GraphQL Provider Which GraphQL provider they are using? (e.g Apollo? Yoga?) | Postgres Instance Do they have an existing Postgres database? | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | Passport | Front-end App + SDK | Active ✅ | ✅ | Hirenodes? TBC | ✅ | ✅ | | ✅ | | Oamo | Front-end App + soon SDK? | Active ✅ | ✅ | Self-hosted? TBC | | | | | | Akasha | SDK | Active? | Testnet | | ✅ | ✅ | Apollo | ✅ | | Index.Network | SDK + Backend? | Active ✅ | ✅ | Self-hosted | ✅ | ✅ | | ✅ | | ZUCITY | | | | | | | | | | Iggy Social | | | | | | | | | | Latteral (Coordination.network) | | | | | | | | | | Molecule | | Interested in OrbisDB | | | | | | | | Plurality | | Interested in OrbisDB | | | | | | | | | | | | | | | | |

Technical context (to be fill-in above)

It will be extremely helpful to understand precisely what is the current status of ComposeDB builders to offer a targeted migration/compatibility approach for each of them based on their technical stack.

• Where do they host their node?
  • Hirenodes?
    • If no: Details about their own server hosting
• Do they use ComposeDB libraries for write (probably yes)?
  • If yes: Mutation examples?
  • If no: How do they write data?
• Do they use ComposeDB GraphQL endpoint for reads (probably yes)?
  • Which GraphQL provider they are using?
  • If yes: Example of queries and relations?
  • If no: How do they query content?
• Do they have an existing Postgres database
• Details about their project
  • Are they building an SDK?
  • Are they building a front end app?
  • Are they building a back end app?