components-guide

Building scalable backends with isolated features involves organizing logic into composable units. You define clear component boundaries for API surfaces and isolated data, then orchestrate these sibling components from a main app.

To integrate Convex components, you configure them within the convex.config.ts file. This allows your main application to orchestrate the encapsulated features and manage their dependencies, references, and assets effectively.

Extracting monolithic backend logic into modular components uses migration patterns to improve maintainability and reuse. You create isolated units with clear boundaries, configure them in convex.config.ts, and orchestrate them as siblings from a main app.

Creating a Convex component requires a SKILL.md file with YAML frontmatter containing name and description. You can also include optional scripts, references, and assets directories to supply dependencies, references, and assets for the component.

You should use isolated components for backend scalability when you need to encapsulate features into reusable units. This approach enforces clear API surfaces and isolated data, enabling composable architectures that are more maintainable than monolithic structures.

Component isolation works by defining clear API surfaces and isolated data for each unit within a scalable backend. This encapsulation allows features to function as modular, composable units orchestrated from a main application without direct interference.