Onwards and upwards, time for our plans going into Q1 (which starts Feb at Convex). Our primary focus is on scaling up and improving the experience for growing teams that are already heavily invested in Convex.
Scale up and out
There are a lot of projects lined up to improve internal Convex scalability but the tasks that most directly affect users are:
* Speed up code sync for large codebases.
* Finish deploying Fun Run to increase the level of parallelism we can support.
Plans and Billing
This is mostly an internal project to decouple our plans and billing from our backend codebase so we can iterate more quickly on providing ideal pricing to users. User-visible tasks include:
* Don't charge for cached database reads.
* Make cached function calls cheaper.
Debugging and Profiling
We pride ourselves on Convex just working out of the box but there are times when some additional insight is required into why a function isn’t performing well. We can do a lot better to help folks help themselves:
* Allow logging of execution time within a function.
* Stream logs out of long-running or failed functions.
* Log system errors more clearly.
* Add support for fine-grained tracing of function execution.
* Preemptively notify customers who are getting close to execution limits.
* Better local testing and unit testing support.
* Publish best practices for monitoring and alerting for customer projects.
Open Source
Finish the swing on open sourcing the core of the Convex backend. The main remaining tasks are extending the CLI to provide better support for managing a local backend. This will be a single-binary version of the Convex backend that is intended for testing and running locally, not the highly durable scale-out distributed system we run customer backends on.
We’re looking forward to getting these changes out! Our community is growing quickly and we think this set of projects will get us well ahead of both the influx of customers and larger projects onboarding to the platform.
Scale up and outThere are a lot of projects lined up to improve internal Convex scalability but the tasks that most directly affect users are:
* Speed up code sync for large codebases.
* Finish deploying Fun Run to increase the level of parallelism we can support.
Plans and BillingThis is mostly an internal project to decouple our plans and billing from our backend codebase so we can iterate more quickly on providing ideal pricing to users. User-visible tasks include:
* Don't charge for cached database reads.
* Make cached function calls cheaper.
Debugging and ProfilingWe pride ourselves on Convex just working out of the box but there are times when some additional insight is required into why a function isn’t performing well. We can do a lot better to help folks help themselves:
* Allow logging of execution time within a function.
* Stream logs out of long-running or failed functions.
* Log system errors more clearly.
* Add support for fine-grained tracing of function execution.
* Preemptively notify customers who are getting close to execution limits.
* Better local testing and unit testing support.
* Publish best practices for monitoring and alerting for customer projects.
Open SourceFinish the swing on open sourcing the core of the Convex backend. The main remaining tasks are extending the CLI to provide better support for managing a local backend. This will be a single-binary version of the Convex backend that is intended for testing and running locally, not the highly durable scale-out distributed system we run customer backends on.
We’re looking forward to getting these changes out! Our community is growing quickly and we think this set of projects will get us well ahead of both the influx of customers and larger projects onboarding to the platform.
