Vote on features you want to see built. Back requests with Convex Chips to influence priority.
Allow components to define "use node" actions.
Convex currently enforces its own _id primary key for all tables which is problematic and sub-optimal performance-wise in various use cases: Migrating data from previous databases to preserve primary keys/relationships Using 3rd parties as the source of truth for primary keys e.g. Clerk users, orgs,…
Provide caching at the "sub query" level inside the convex deployment. Specifically if a developer calls ctx.runQuery(...) within a query or mutation, and that individual query's cache value is still valid, the cached value will be used instead of running v8 again. This will allow developers to cont…
To better handle background jobs
Convex cloud provides global edge caches that serve cached queries at low latency everywhere on earth.
Allow Convex deployments to be provisioned in Canada.
Support inexpensive copy-on-write database clones so teams can create realistic test environments and reproduce bugs without paying full storage costs each time.
Improve analytical workloads with better support for reporting, aggregations, warehouse-style queries, and downstream BI integrations without compromising transactional workloads.