In all honesty is it a good idea to use
In all honesty is it a good idea to use convex primarily as your backend OR is it better to use convex alongside another backend? While Convex has some really desirable features it also has a lot of features that are missing. Are there any examples of large scale apps using Convex? And what would others recommend?
6 Replies
It's designed to be your whole backend, and plenty of apps use it that way. What are the missing parts that stand out to you most?
Are there any examples of large scale apps using convex as their whole backend?
But what I'm currently missing:
* Next.js Server Rendering
* More consistent backups and longer backup retention.
* Convex EU region
We'll have more examples that we have permission to talk about, but I know I can point to Candle: https://discord.com/channels/1019350475847499849/1280663018581131274/1421272726705803356
Nextjs server rendering works great with Convex, EU coming soon, can you say more on expected vs actual for backups?
Nextjs server rendering works great with ConvexThough it's in beta? Currently it would be too much of a loss if there was the possibility of losing a day of data
Yeah we have some long lived betas - server rendering via preloadQuery and friends works well. For backups, you can also backup as often as you like via cli: https://docs.convex.dev/database/import-export/export
Data Export | Convex Developer Hub
Export your data out of Convex
It's project dependant, but I have a project where Convex is the central orchestrator, and other backends (Python FastAPI servers) speak to it to update their state
So you can use Convex with other backends but it depends on what why you'd need to, in my case, it's for GPU workloads
The reactive subscription works well from the Python client on server -> Convex so all servers immediately can react to state changes (ie. receiving a new work order)