I am using Durable Objects to make a service for an app since my model allows me to instantiate a DO
I am using Durable Objects to make a service for an app since my model allows me to instantiate a DO per user, this way I don't run into the 10GB limit a single D1 database would have. The only issue is that some power users will definitely exceed this limit and I'll have to shard the data across multiple instances.
When writing to the underlying SQL database I don't know how much space the inserted data will take up. I would like a way to:
I really would like not to have a "attempt to write, if it's 0.9GB move to another shard just in case" scenario.
When writing to the underlying SQL database I don't know how much space the inserted data will take up. I would like a way to:
- start something like a transaction;
- attempt to insert data;
- if succeeded, return;
- if failed (due to storage cap), rollback, and move to next shard.
I really would like not to have a "attempt to write, if it's 0.9GB move to another shard just in case" scenario.
