BusConfiguration
Last updated
Last updated
Creates a configuration in order to initialize a new BusInstance.
Registers a class handler that receives a message and performs a unit of work. When Bus is initialized it will configure the transport to subscribe to the type of message handled by the handler and upon receipt will forward the message through to the handle()
function.
Argument | Description | Default |
---|---|---|
Registers a function handler that receives a message and performs a unit of work. When Bus is initialized it will configure the transport to subscribe to the type of message handled by the function handler and upon receipt will forward the message to the function.
Registers a custom handler that receives messages from external systems, or messages that don't implement the Message interface from @node-ts/bus-messages.
See also System messages.
Registers a workflow definition so that all of the messages it depends on will be subscribed to and forwarded to the handlers inside the workflow.
See also Workflows.
Configures Bus to use a different transport than the default MemoryQueue.
See also Transports.
Configures Bus to use a different logging provider than the default consoler logger.
See also Loggers.
Configures Bus to use a different serialization provider. The provider is responsible for transforming messages to/from a serialized representation, as well as ensuring all object properties are a strong type.
See also Serializer.
Configures Bus to use a different persistence provider than the default InMemoryPersistence provider. This is used to persist workflow data and is unused if not using workflows.
See also Persistence.
Sets the message handling concurrency beyond the default value of 1, which will increase the number of messages handled in parallel.concurrency
Use a local dependency injection/IoC container to resolve handlers and workflows.
Configures Bus to use a different persistence provider than the default InMemoryPersistence provider. This is used to persist workflow data and is unused if not using workflows.
See also Dependency injection.
Run custom middleware before/after the point a message is read from the transport and then dispatched to handlers and workflow handlers.
See also Middleware.
Configure the bus to use a different retry strategy instead of the default.
See also Retry Strategies.
Initialize a configured BusInstance. This should be called after all options have been provided for the configuration.
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
Argument | Description | Default |
---|---|---|
classHandler
A class responsible for handling messages that implements Handler
None
functionHandler
A functional handler mapping initialized using handlerFor
None
messageHandler
A handler that receives the custom message
None
customResolver
A discriminator that determines if an incoming message should be mapped to this handler
None
workflow
Workflow definition to register
None
transport
A configured transport to use
None
loggerFactory
A factory that creates a new logger
None
serializer
Serializer to use
None
persistence
Persistence provider to use
None
concurrency
The number of messages that can be handled in parallel
None
containerAdapter
An adapter that allows Bus to resolve class instances from the underlying IoC container
None
middleware
A middleware function that will be executed after a message is read from the transport and before it is dispatched to handlers.
None
retryStrategy
An implementation of RetryStrategy
that calculates the delay between retrying failed messages.
DefaultRetryStrategy