Use safe data format for writing data to backends

Open Neverlord opened this issue 5 years ago • 1 comments

As outlined in https://github.com/zeek/broker/pull/160, Broker currently serializes data using caf::binary_serializer and caf::binary_deserializer in its backends. This is unsafe, because the binary format may change between CAF releases. This means any CAF upgrade may break the persistent state of Broker.

We can either avoid binary formats in the first place, e.g., by using JSON, or we should implement a custom serializer and deserializer with a data format that Broker controls. That would also enable us to embed versioning information.

Dec 19 '20 14:12 Neverlord

This may become obsolete if we switch to a memory-mappable message representation.

Aug 12 '21 15:08 Neverlord