> All data is serialisable. I'd say that's axiomatic. Data is information with a concrete representation. I Do not disagree. I think the problem comes from us

> All data is serialisable. I'd say that's axiomatic. Data is information with a concrete representation. I Do not disagree. I think the problem comes from us using the term serializable to liberally. > My best guess is there's some limitations caused by the stack under your implementation that you haven't worked around, but I don't know what those limitations are or which ones you plan to resolve. Agree. Feedback received, and thanks. This will be worked in. But I'll attempt to answer your questions here: > Is aliasing within the original preserved? No. The data being sent over the network is copied by value, not reference - if that makes sense. > Is it compressed in transit? Yes. With Message Pack. > Is it delta encoded with respect to information that was sent previously? I'm not sure I follow, but all calls are independent of each other. > Is there some initial blob of information every instance starts up with that messages are deduplicated against? > And that's before the behaviour on mutation - when one machine changes the data, how and when is that change reflected on other machines? Not sure if this helps, but this [1] talks about the architecture. There's a C&C. The control-plane is the orchestrator for all machines. [1] https://docs.differential.dev/advanced/architecture/ https://docs.differential.dev/advanced/architecture/