I did see I can move it to a
I did see I can move it to a horizontally scalable db with HA like Postgres, do you know the backend server itself can be horribly scaled or sharded in any way? I read somewhere that you are hard limited to a single instance.
3 Replies
self-hosted and cloud have largely the same code.
There are some differences in deployment around splitting out the function running service for economies of scale to offer lower prices, but it's all the same code.
Re containers - you can do whatever you want. Edit the dockerfile / docker-compose to your hearts content and make what you need.
Self-hosted out-of-box is limited to one
convex-local-backend instance which for most normal sized production apps is plenty good enough w/ vertical scaling. The underlying persistence database can swapped out to whatever service you like (RDS, Planetscale, Neon, whatever).
If you want to use the cloud service, we'll make sure everything is tuned to work well at scale and grow with you in exactly the ways you scale in practice.Thank you. Due to customer requirements (that may or may not make sense) I don't think my company will be able to adapt this technology.
Question, as this is semi relevant to me: outside of sharding, is there a way to horizontally scale when self-hosting?
If there's a compute intensive task, I'd prefer not to have to throw it on an external services sometimes, but it sounds like that might be required with that limitation.
I totally get that self-hosting is the primary scenario you're trying to optimize for (for obvious reasons), but I do like the idea of (in theory) being able to run things myself.
I've run my own startup, and realying on another for core infrastructure if there's no path to run it yourself - even just to bridge some rewrites - is something i'm not 100% comfortable doing.