NI just finished the tutorial and I have some questions
* Can Convex do local-first? Work offline and sync later?
* Is it possible to run your own convex reactor? (Like github co-location)
* Do companies need to worry about Convex having access to their data?
* This is vendor lock-in, right?
* What happens if you exceed the maximum quotas?
* What happens if Convex raises their prices?
* Can Convex afford to host all this? What if they run out of money?
* How granular are “ready-sets”? Down to the record? Down to the xpath within a record?
* How do queries that use randomness or the date decide when to be updated?
* This “likes” example looks like an N+1 query problem.
* Is it going to cause performance issues or not?
* Will we ultimately want to write it a different way?
* How does its performance compare to postgres?
* This would be a good opportunity to introduce uniqueness constraints so you can’t double-like the same document. Can we do that?
* can the scheduler debounce things?
* Specifically, I’d like to schedule something to occur immediately, but if it is scheduled again within 5 seconds it should wait until the end of that period before executing again, no matter how many times it is called in between.
* access control
* how do you configure which actions/mutations/etc are available on the client side vs the server side?
* how do you configure what’s available to a specific user?
* can I use bun and not use node?
* Is it possible to run your own convex reactor? (Like github co-location)
* Do companies need to worry about Convex having access to their data?
* This is vendor lock-in, right?
* What happens if you exceed the maximum quotas?
* What happens if Convex raises their prices?
* Can Convex afford to host all this? What if they run out of money?
* How granular are “ready-sets”? Down to the record? Down to the xpath within a record?
* How do queries that use randomness or the date decide when to be updated?
* This “likes” example looks like an N+1 query problem.
* Is it going to cause performance issues or not?
* Will we ultimately want to write it a different way?
* How does its performance compare to postgres?
* This would be a good opportunity to introduce uniqueness constraints so you can’t double-like the same document. Can we do that?
* can the scheduler debounce things?
* Specifically, I’d like to schedule something to occur immediately, but if it is scheduled again within 5 seconds it should wait until the end of that period before executing again, no matter how many times it is called in between.
* access control
* how do you configure which actions/mutations/etc are available on the client side vs the server side?
* how do you configure what’s available to a specific user?
* can I use bun and not use node?
