Guide to using Convex components for feature encapsulation. Learn about sibling components, creating your own, and when to use components vs monolithic code.
Self-contained mini-backends that bundle schema, functions, and data with clear API boundaries. Components encapsulate features like storage, payments, and notifications as reusable backend modules, reducing monolithic code and improving maintainability Sibling components pattern allows multiple components to work together at the same level, with the main app orchestrating calls across them Official component library includes authentication, storage, payments, AI, and utility components like rate limiting, migrations, and workflow orchestration Create custom components for self-contained, reusable features; components cannot directly access parent app tables or call each other, maintaining isolation Convex Components Guide Use components to encapsulate features and build maintainable, reusable backends. What Are Convex Components? Components are self-contained mini-backends that bundle: Their own database schema Their own functions (queries, mutations, actions) Their own data (isolated tables) Clear API boundaries Think of them as: npm packages for your backend, or microservices without the deployment complexity. Why Use Components?
don't have the plugin yet? install it then click "run inline in claude" again.