Hi, Jesse, our one example for spawnUri() at the moment is a unit test:
spawnUri() creates an isolate, loads code into it, and runs that. The physical location where this isolate is created isn't specified; currently it's local to the caller but it could be done on the remote server, with their consent. As requested by the caller, or by the code being run, or conceivably auto-migrated for best performance. You'd then end up with a communication port open to a persistent remote process that may take advantage of its colocation with other server code and data, or of faster hardware or better bandwidth than you've got locally
Is that the type of thing you're looking for? If you have a use in mind I'd be interested to hear more about it, since we really haven't hashed out use cases yet.
Eli