Forum ‹ BigDB ‹ Pricing Clarification

[Claytonious]

It seems that pricing is based on "number of objects", without any reference to the size of those objects. Is this correct? For example, if I have 300,000 objects that are 1 byte each, I would be charged for 300,000 objects according to my paid plan. But if I had only a single object of 300,000 bytes, I would only be charged for 1 object?

[Henrik]

Yes.

But note that when you fetch an object you get the entire object, and that counts towards your bandwidth bill, so there are good reasons to have smaller objects sometimes. In the end, you're free to optimize it for what's best for your game.

[HybridMind]

What exactly counts as an "object" in the database?

For example, if I have a highscore table that tracks 2 records, score and playername, and have only top 10 records tracked, is that just 20 "objects" ?

Also, Does a read or write call to BigDB count as as concurrent connection?

Thanks!

[dreamora]

every distinct object which you can load by name or browse to / search for in the dashboard here on the page is a different DB object.

So if each of the table only contains 10 elements (cause you delete the old or overwrite it) then yes thats 20 objects. But if you have 10000 objects and only read out the top 10, then it would still be 20k objects.