components-guide

Organize backend features by creating self-contained components with isolated data schemas and functions, then wire them into your project using convex.config.ts to ensure reusability and maintainability across your application.

A modular backend architecture in Convex separates features like storage and authentication into isolated components with defined boundaries, separate schemas, and configurable wiring to enable teams to structure, reuse, and compose large applications.

Wire a reusable component into your Convex project by configuring it within the convex.config.ts file, which adapts the isolated component to your specific project architecture and connects its defined API boundaries.

Yes, you can compose multiple isolated features like storage, authentication, notifications, and analytics by structuring them as independent components and wiring them together in convex.config.ts to build larger applications.

Isolate data and API surfaces by encapsulating features into self-contained components with their own schemas and functions, establishing clear API boundaries that prevent cross-feature interference and improve maintainability.

Use component-based architecture when you need a scalable way to organize backend features into reusable, isolated components, especially when building large applications that require clear API boundaries for features like storage and authentication.