puchesjr
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
Yes, once we get to 50,000,000 reads we'd updates we would need to work with you all on that pricing.
27 replies
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
so in firestore, you are charges the 1,000 document reads for each person connected + 1 for your devices document update.
if i understand convex properly, this will not be the case, we will be charged for the bandwidth once the websocket is connected/established, but i would like clarification here
27 replies
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
final question, how is the real-time updates charged? if i understand the docs, i'll be charged for the initial function call which should establish the websocket connection, and then i'll be charged for the bandwidth, but if the connection breaks and has to reconnect, are we charged again?
are we charge for a function call per update that comes down the wire? or is it only the initial connection?
27 replies
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
now, what is less clear to me is how the real-time updates are charged, are we charged for the real-time update when the documents are changed? or are we only charged 1x for the connection and any possible reconnections, as well as bandwidth
27 replies
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
that is what i am trying to calculate / forecast now.
to give you an idea why i was trying to understand the function cost.
with firestore - because this is what we were considering staying with, the price per document read is $0.06 per 100k and the cost for writes is $0.18 per 100k. To be clear is this per document read.
convex on the other hand charges per function, if we were comparing single document/record read per service then convex would be much more expensive with growth. but, because they charge per function, and a function can return up to 8MiB of data that implies I can return say 100, 200, 500 records per function call and only be charged for the 1 function call and the bandwidth, as well as storage for the data.
convex, because of the function pricing is a clear winner on writes - because firestore charges $0.18 per 100k writes. which is $1.80 per million, and while convex is $2 per million, you can do multiple writes in the function and you only incur 1x fee. whereas with firestore, when we perform a transaction, we incur a cost for each document we touch - so if we touch 2 documents we incur 2 writes. whereas, with convex we would only have 1 function charge.
now, our system will be a good blend of reads and writes, but it is a shade heavier on the writes. Think accounting where you will make a bulk read of data, and then you will update documents like invoices paid, parts added, etc.
27 replies
CCConvex Community
•Created by puchesjr on 4/2/2025 in #general
Convex pricing model
Not worried about the pricing, trying to be conscious of how it is priced. Built a pretty complex system with couchdb, and recently Firestore where we are charged per read/write/delete. we were performing hundreds of millions of reads per month.
We took great care in denormalizing our data to match our reads and optimized for that use case.
I love everything I’ve read and everything dug into about convex. Now that we are starting a new project, I want to give it a full go. But, I have a budget and need to be sure I account for the spend and forecasted spend as we grow
27 replies