Oreally liked the convex.sucks podcast
really liked the convex.sucks podcast one more concern I have is this;
Convex bills per function call and architecture sort of forcing for nested calls e.g. I have an action that
1) runs a query to get current user then
2) runs a query to get users subscription details then
3) runs a mutation to create; lets say atodo item then
4) runs a mutation to update user's todo item quota
which means 5 calls for 1 main user action
for every other case e.g. host your api in vercel, lambda, etc this is still 1 function call
are there any plans to optimize this?
Convex bills per function call and architecture sort of forcing for nested calls e.g. I have an action that
1) runs a query to get current user then
2) runs a query to get users subscription details then
3) runs a mutation to create; lets say atodo item then
4) runs a mutation to update user's todo item quota
which means 5 calls for 1 main user action
for every other case e.g. host your api in vercel, lambda, etc this is still 1 function call
are there any plans to optimize this?
