Looking over the docs again, I am actually kind of curious why there isn't a way to spawn a DO at a specific location or minimal latency to a specific CF POP. I wonder if it's a engineering limitation or just lack of demand (I'm guessing I will probably never get a specific answer)
I switched to my phone hotspot and get Melb on the cdn-cgi trace but the Worker calls still being routed through Perth. I think I'd better ignore this or it'll send me crazy
Now while Ive been loooking at this DO site the Perth option has disappeared from Melbourne entirely hopefully someone has seen me complaining and is fixing this as we speak
But, yes, your observation and what others said above is mostly true that a DO will be created in the initially created colo if possible. There are cases it will move out of that, like when that colo has network issues and is taken out of the network for a while and the DOs hosted there will move elsewhere in the same region.
In the long-term future, our hope is for DOs to be moving more often closer to requests, but not yet.
At the moment, yes, we have a record of all created DOs even without storage. As I said, though, I wouldn't depend on this because we want to change it in the future. Just explaining why you are seeing the stickiness.
Anyone used DOs to ingest/process WebRTC streams over WebSockets? I wanna export a frame of a stream every X frames and send it off to be processed elsewhere. I know about Realtime and stuff but there're other processes that would interact with this and benefit from it being on DOs