If you need a database for online workloads (ie, your users interact with your product via reading and writing data to the database) and are ok with writing your backend in JavaScript or TypeScript, you should consider Convex.
If you need for example peer-to-peer video or machine-learning inference, these are not well suited to building on Convex from scratch, but you can likely use Convex to implement the rest of the app (and probably use another service for these).
Since Convex is online and realtime, it doesn't focus on domains like embedded systems programming or analytics (but you can stream data from Convex to an analytics platform).
Comments
Great workflows! If I was starting a new project today, what are the cases where I should consider Convex vs. not?
If you need a database for online workloads (ie, your users interact with your product via reading and writing data to the database) and are ok with writing your backend in JavaScript or TypeScript, you should consider Convex.
If you need for example peer-to-peer video or machine-learning inference, these are not well suited to building on Convex from scratch, but you can likely use Convex to implement the rest of the app (and probably use another service for these).
Since Convex is online and realtime, it doesn't focus on domains like embedded systems programming or analytics (but you can stream data from Convex to an analytics platform).