> that they should be architecting their app for autocleanup/storing IDs somewhere I still don't agr
that they should be architecting their app for autocleanup/storing IDs somewhereI still don't agree with this. Autocleaning are very different things from storing IDs.
You almost always want to have a way to get the DO ID from within your application. You cannot always trust users telling you which DO ID they have access to, you need to serve List APIs, and hundreds other use cases. Even if don't store literally the DO IDs, you should have a deterministic way of generating that ID. Otherwise it's a black hole. Like any other storage product, when an entity/account/resource will be deleted you need to do cleanup. Same applies for R2, for DOs, for SQL databases when the IDs are random, and the list goes on.
Autocleaning, not sure where this fits. Maybe just for temporary ephemeral data you want to delete after a TTL, but again, there shouldn't be magic, you design around this deletion.
Maybe it's just me, but I don't want providers to be deleting my data on their own or through something I didn't explicitly configured/coded.
