Is msgspec suitable for high-performance serialization of binary data?

I have a small number of large numpy arrays (1-100MB total) stored in a structured way, with some additional JSON metadata. Something like:

{
    "my_array": numpy.array([0, 1, 2, ...]),
    "list_of_array": [numpy.array([0, 0, 0]), numpy.array([1, 1, 1]), ...],
    "dict_of_arrays": {"a": numpy.array([0, 0, 0]), "b": numpy.array([1, 1, 1]), ...},
    "some_metadata": "blah",
    "some_other_metadata": {"a": 1, "b": 2}
}

Let's say I want to send data structures like that over a socket (e.g., zeromq). I could pickle, but would prefer a serialization format that's more version- and language-agnostic.

Is msgspec (in JSON or msgpack mode) suitable for this use case? Are there any other considerations I should keep in mind? (I know a couple years ago a lot of work went into pickle5/dask comms to make serialization zero-copy and fast for this kind of use case.)

Start with the issue's examples of numpy arrays, JSON or MessagePack encoding, and socket or ZeroMQ transfer. Determine whether the repository identifies an existing entry point or test for binary-array serialization; done would require a defined, version- and language-agnostic approach with its performance and compatibility considerations documented.