I also suggest folks to stop thinking about DOs in terms of "created" and "destroyed". It's a mindsh
I also suggest folks to stop thinking about DOs in terms of "created" and "destroyed". It's a mindshift, but it will simplify lots of things for your architecture designs. A term commonly used is "virtual objects".
You just access it and use it. If it doesn't exist, it will be created, and if it was already accessed before you will be routed to the same instance. Forget about the classical management of server instances.
The only case you need to care about lifecycle management, is if you want to stop paying for an object's storage, and again, you don't "destroy it", you just access it as usual and
You just access it and use it. If it doesn't exist, it will be created, and if it was already accessed before you will be routed to the same instance. Forget about the classical management of server instances.
The only case you need to care about lifecycle management, is if you want to stop paying for an object's storage, and again, you don't "destroy it", you just access it as usual and
deleteAll() its storage. That's it. Storage gone, the object lives forever though, you can still access it and write new data later if needed, or never access it again.