Durable Objects Pricing for Batch Operations

There are operations like put, get, list, delete that all allow you to operate on batches of DO storage keys.

Based on this articles:

We chose to meter our requests in 4 KB increments across the board to provide the lowest prices with the greatest flexibility. Deletes do not have a size limit.

Does this mean that for a batch of storage keys, we’re only charged based on each 4 KB increment of data that is altered?

Or it charges per key minimum and additionally on each 4 KB increment for the value of the key (max 32 KB vals for each key?

Would you happen to know @ckoeninger ?

Hey Matt!

It’s per key. So, if you have 20 keys in your operation, that would count as a minimum of 20 reads, possibly more if those keys were large.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.