What problem does it solve?
Convex apps often become hard to maintain when backend logic grows into a monolithic set of tightly coupled functions. This guide helps you organize backend features into isolated, reusable Convex components with clear boundaries.
Core Features & Use Cases
- Understand component encapsulation: Learn how Convex components bundle their own schema, functions (queries/mutations/actions), and data tables behind an API boundary.
- Adopt the sibling-components pattern: Use multiple components side-by-side for separate concerns like storage, billing, notifications, and analytics.
- Create and document your own components: Follow a repeatable structure for installing, configuring in convex.config.ts, and using component APIs from the parent app.
- Avoid coupling mistakes: Prevent illegal or fragile designs where a component tries to access parent app tables.
Quick Start
Use this guide to refactor one growing backend area (like uploads, rate limiting, or analytics) into its own Convex component and then call it from your main app through components.<name>.