This section outlines the planned future development for LiteBus.

LiteBus is primarily an in-process mediator, but there are plans to provide integrations with distributed messaging systems:

• RabbitMQ Integration: Connect LiteBus with RabbitMQ for distributed message processing
• Kafka Integration: Support for publishing and consuming messages with Apache Kafka
• Azure Event Bus Integration: Integration with Microsoft Azure Event Bus

Long-term plans include adding support for sagas (process managers) to coordinate complex workflows across multiple message handlers.

Planned support for the outbox pattern to ensure reliable message delivery in distributed systems, helping to maintain data consistency across service boundaries.

Improved capabilities for parallel message processing, including:

• Configurable parallelism settings
• Thread-pool optimizations
• Better control over concurrent execution

LiteBus welcomes community contributions. Areas where community help would be particularly valuable include:

• Additional integration adapters for messaging systems
• Performance optimizations
• Enhanced documentation and examples
• Test coverage improvements

If you have feature requests or suggestions for LiteBus, please submit them through:

1. GitHub Issues: https://github.com/litenova/LiteBus/issues
2. Discussions: https://github.com/litenova/LiteBus/discussions

All feature requests will be evaluated based on alignment with the project's goals, maintainability, and community benefit.

LiteBus follows a feature-driven release schedule rather than a time-based one. New versions are released when significant features or improvements are ready.

Minor releases with bug fixes and small improvements are made as needed to address issues reported by the community.