Integrations
Integrations
Databases, MongoDB, OpenAPI, filesystems, CodeSQL, and federation.
Integrations explain how GraphJin exposes external systems as first-class graph surfaces while preserving the same policy model.
| Page | Integration pattern |
|---|---|
| Multi-Database | Root-level result merging, cache isolation, table mapping, and nested database joins. |
| MongoDB | GraphQL compiled to a JSON DSL and translated into MongoDB aggregation pipelines. |
| OpenAPI | Remote API operations exposed as root fields or joins on database rows. |
| Filesystem Tables And Uploads | Local, S3, and GCS object stores exposed as queryable virtual tables. |
| CodeSQL | Source-code indexes for files, symbols, refs, docs, and guarded source edits. |
| Apollo Federation | Federation v2 SDL and entity resolution for database-backed subgraphs. |
The shared rule is that each external surface becomes part of the same compiled graph. GraphJin still applies auth context, source capabilities, cache boundaries, and allow-list behavior before it calls the backend.
Multi-Database
Map tables across named databases while preserving routing and cache isolation.
MongoDB
GraphJin generates JSON DSL that the MongoDB driver translates into aggregation pipelines.
OpenAPI
Expose selected OpenAPI GET operations as root fields or row joins in GraphQL.
Filesystem Tables And Uploads
Expose local, S3-compatible, and GCS object storage as GraphQL tables.
CodeSQL
Index source trees into queryable tables for symbols, references, imports, docs, and parse diagnostics.
Apollo Federation
Expose GraphJin as a database-backed Apollo Federation v2 subgraph.