Add rate limiting for serialization

**Feature request**
It would be great to have retry for handlers.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_retry` with default `false`.

The issue names no files, tests, or entry points; first locate the serialization path, handler code, and configuration handling. Done should include a documented default-disabled enable_retry option and defined retry behavior for handlers, with tests covering the resulting behavior.

Written by the indexing model from the issue text.