Basic Structure
YAML Configuration
Minimal Configuration
With Client Name
Production Configuration
Programmatic Configuration
Using Builder Pattern
Using Data Class
Loading Configuration
From YAML File
From Resource
From String
Configuration Options
| Option | Type | Default | Description |
|---|---|---|---|
name | String | null | Optional client identifier for logging and monitoring |
transport | Object | Required | Transport configuration (see Transport Configuration) |
Using the Client
Creating a Client Instance
Dispatching Tasks
Starting Workflows
Using Tags
Multiple Environments
You can create different configurations for different environments:Development
Staging
Production
Environment Variables
You can use environment variable interpolation in YAML:Client Lifecycle
Starting the Client
Closing the Client
Best Practices
Connection Pooling
- Reuse client instances - Create one client per application, not per request
- Connection sharing - Multiple threads can safely share a single client instance
- Proper shutdown - Always close clients to release resources
Configuration Management
- Externalize configuration - Keep configuration files separate from code
- Environment-specific configs - Use different files for dev/staging/production
- Secret management - Use environment variables for sensitive data
Error Handling
See Also
- Transport Configuration - Configure message transport
- Worker Configuration - Configure workers to process tasks