Serializers registered with the service. We store the DI keys and realize them as needed, rather than at register time since most registration is done via the
decorator and the ContainerBlueprint. Realizing them at that time can cause loops in the DI call to realizeContainer since getContainer() -> realizeContainer() -> make the serializer -> getContainer(). This largely defers the realization until after all the DI keys are registered with the global Container.
Decode a serial payload to the original object using a registered serializer, if one exists.
Encode a value to its serial payload using a registered serializer, if one exists.
Register a new serializer with the service.
Register an already-realized serializer instance with this service.
Service that manages (de-)serialization of objects.