User function Snapshot and Event formats about cloudstate HOT 3 OPEN

I'm interested in this from the "Language X" and its Client API perspective.

The format used is transparent for the proxy, isn't it?

A Python client may pickle its events; JS probably use JSON and Go use gob or protobufs... or any other preferred format. This might vary if "Function Code" implementations can be mixed at the same time or one expects to have snapshots persisted over a long time and Function Code has expectations about persisted data to be migrate-able over time.

from cloudstate.

@marcellanz Yes, the format should be opaque to the proxy, but of course this has implications over time for maintenance, interoperability if one wants to rewrite a function from one language to another.

from cloudstate.

How much of this issue is "answered" by 46d1dc8 and CloudState serialization convention? The later explains the conventions how a different format should be implemented for CloudState.

Perhaps, it could be explicitly documented why the convention is relevant even if opaque to the proxy and why "stability of the encoded form" is important in this case.

from cloudstate.