ReplicatorMessageSerializer

Produces an object from an array of bytes, with an optional type-hint.

It's recommended to throw java.io.NotSerializableException in fromBinary if the manifest is unknown. This makes it possible to introduce new message types and send them to nodes that don't know about them. This is typically needed when performing rolling upgrades, i.e. running a cluster with mixed versions for while. NotSerializableException is treated as a transient problem in the TCP based remoting layer. The problem will be logged and message is dropped. Other exceptions will tear down the TCP connection because it can be an indication of corrupt bytes from the underlying transport.

Return the manifest (type hint) that will be provided in the fromBinary method. Use "" if manifest is not needed.

Serializes the given object into an Array of Byte.

Note that the array must not be mutated by the serializer after it has been returned.

Java API: deserialize with type hint

Java API: deserialize without type hint

Produces an object from an array of bytes, with an optional type-hint; the class should be loaded using ActorSystem.dynamicAccess.

Returns whether this serializer needs a manifest in the fromBinary method

Actor system which is required by most serializer implementations.

Configuration namespace of serialization identifiers in the reference.conf.

Each serializer implementation must have an entry in the following format: org.apache.pekko.actor.serialization-identifiers."FQCN" = ID where FQCN is fully qualified class name of the serializer implementation and ID is globally unique serializer identifier number.

Globally unique serialization identifier configured in the reference.conf.

See pekko.serialization.Serializer.identifier.