developing-funboost-broker

Subclass AbstractPublisher and AbstractConsumer, implement the abstract methods like _publish_impl and _dispatch_task, then call register_custom_broker with a broker name. Use that name as broker_kind in BoosterParams when decorating functions with @boost.

A custom Publisher must implement four abstract methods: _publish_impl for the core publish logic, clear to purge the queue, get_message_count to return queue depth, and close to release connections. The custom_init hook is optional.

Yes, use consumer_override_cls or publisher_override_cls in BoosterParams to mix in a custom class that overrides methods like _submit_task. The mixin should call super() so the original broker behavior is preserved.

The _dispatch_task loop must call self._submit_task with a kw dictionary containing a body key for every message. Also verify the broker is registered in the factory mapping if using static extension, and that _dispatch_task blocks rather than returning immediately.

Use register_custom_broker when adding a new broker from user code without modifying the framework. Use static extension only when contributing a core broker to funboost itself, which requires updating BrokerEnum, connection configs, and the factory mapping.