components-guide

To organize backend features into reusable components, place your code under the convex/components/<name> directory and register it in convex.config.ts. This encapsulates features with their own schema, functions, and data, creating clear API boundaries for modular architectures.

Reusable backend components are self-contained units that isolate data, APIs, and logic to reduce coupling. You need them when building modular architectures requiring independent deployment, multi-tenant setups, or plugging components across different features and modules.

Yes, the sibling components pattern supports multi-tenant backend architectures by isolating data and logic into reusable units. This enables teams to plug components across features and modules while maintaining clear API boundaries and independent deployment.

The best way to reduce coupling in a modular backend architecture is using self-contained components with their own schema, functions, and data. This canonical component pattern isolates logic into reusable units, enabling independent deployment and composition across features.

To register a new component in convex.config.ts, first create your code under the convex/components/<name> directory. This establishes a frontmatter-based identity for the component, providing a dedicated workspace with optional scripting and reference assets.

Yes, you can compose multiple self-contained components with separate schemas. This design pattern allows teams to encapsulate distinct features independently, enabling modular feature encapsulation across a project while maintaining clear API boundaries between each component.