Dop: Distributed Object Protocol
This is an interesting idea, but it&#x27;s not clear to me that this is going to work at sufficient scale. This isn&#x27;t clear to me because instead of getting a decent white paper on the implementation, we need to learn how this protocol works through what amounts to a PowerPoint. Sure, the slides are nice and simple, but I need more concrete answers on things like how consensus is determined and how available nodes recover from a disaster.<p>The slides suggest that a sufficiently complex system will almost immediately get out of sync. The dependency on upstream nodes asserting state about objects before they are acknowledged and successfully applied by the &quot;owner&quot; node means that some subset of nodes will be working on assumptions that haven&#x27;t been validated by objects they don&#x27;t in fact own. This seems to conflict with what prior slides say about who can mutate objects.<p>I think distributed object management is a useful concept, but instance state needs to be owned and managed by multiple nodes for redundancy in anything remotely approximating a production-level system. That doesn&#x27;t seem to be readily addressed anywhere, either. I&#x27;d love to read more about this with the level of detail you&#x27;d need from a system that readily has use cases and reference architectures instead of possibilities.