Basic Configuration
ASP.NET Core Application
Configure SimpleMessageBus in yourProgram.cs file:
Console Application
For console applications, use the generic host:Provider-Specific Configuration
Azure Storage Queue
Basic Configuration
Basic Configuration
Managed Identity
Managed Identity
Custom Queue Naming
Custom Queue Naming
Amazon SQS
Access Key Configuration
Access Key Configuration
IAM Role Configuration
IAM Role Configuration
FIFO Queue Configuration
FIFO Queue Configuration
File System
Basic Configuration
Basic Configuration
Azure Functions Integration
Azure Functions Integration
IndexedDB (Blazor WebAssembly)
Environment-Based Configuration
Configuration by Environment
Configuration with Feature Flags
Message Handler Registration
Manual Registration
Assembly Scanning
Conditional Registration
Advanced Configuration
Multiple Providers
Use different providers for different message types:Custom Dispatcher Configuration
Configure message dispatching behavior:Serialization Configuration
Customize JSON serialization:Configuration Best Practices
1. Use Configuration Sections
Organize configuration inappsettings.json:
2. Environment-Specific Settings
Use different configuration files per environment:3. Secure Configuration
Store sensitive values in Azure Key Vault or AWS Secrets Manager:4. Configuration Validation
Validate configuration at startup:Monitoring and Observability Configuration
Logging
Configure structured logging:Metrics
Configure metrics collection:Health Checks
Add health checks for message bus components:Testing Configuration
Integration Tests
Configure for integration testing:Unit Tests
Mock configuration for unit tests:Troubleshooting Configuration Issues
Connection String Issues
Connection String Issues
Problem: Authentication failures or connection errorsSolutions:
- Verify connection string format
- Check account credentials
- Ensure network connectivity
- Validate queue/storage account exists
Handler Registration Problems
Handler Registration Problems
Problem: Handlers not receiving messagesSolutions:
- Verify handler implements
IMessageHandler - Check
GetHandledMessageTypes()returns correct types - Ensure handler is registered in DI container
- Verify message type matches exactly
Performance Issues
Performance Issues
Problem: Slow message processingSolutions:
- Increase
MaxConcurrentMessages - Reduce
PollingInterval - Optimize handler performance
- Consider batch processing