What problem does it solve? Choosing among 50+ supported message brokers in funboost is confusing, and picking the wrong one can cause message loss, poor performance, or unnecessary infrastructure. This Skill guides you to the right broker_kind based on reliability, deployment, and throughput needs. ## Core Features & Use Cases - Decision Flowchart: Maps reliability and deployment requirements to concrete broker choices like MEMORY_QUEUE, SQLITE_QUEUE, REDIS_ACK_ABLE, and KAFKA_CONFLUENT. - Broker Reference Tables: Lists all broker enums grouped by family (Redis, RabbitMQ, Kafka, MQTT, databases, local files) with trade-off notes. - Connection Configuration: Shows how to set up funboost_config.py with BrokerConnConfig and use broker_exclusive_config without inventing invalid keys. - Use Case: Migrating a task queue from local SQLite to a production Redis setup by changing only the broker_kind parameter, with zero changes to task function code. ## Quick Start Ask the AI which funboost broker_kind to use for a production task queue that needs message persistence and ACK confirmation on an existing Redis server.