Class DistributedCommandBus
- All Implemented Interfaces:
DescribableComponent,CommandBus,CommandHandlerRegistry<CommandBus>
CommandBus that is aware of multiple instances of a CommandBus working together
to spread load.
Each "physical" CommandBus instance is considered a "segment" of a conceptual distributed
CommandBus.
The DistributedCommandBus relies on a CommandBusConnector to dispatch commands and replies to
different segments of the CommandBus. Depending on the implementation used, each segment may run in a
different JVM.
- Since:
- 2.0.0
- Author:
- Allard Buijze
-
Constructor Summary
ConstructorsConstructorDescriptionDistributedCommandBus(CommandBus localSegment, CommandBusConnector connector, DistributedCommandBusConfiguration configuration) Constructs aDistributedCommandBususing the givenlocalSegmentforsubscribinghandlers and the givenconnectorto dispatch commands and replies to different segments of theCommandBus. -
Method Summary
Modifier and TypeMethodDescriptionvoiddescribeTo(ComponentDescriptor descriptor) Describe the properties ofthis DescribableComponentwith the givendescriptor.dispatch(CommandMessage command, ProcessingContext processingContext) subscribe(QualifiedName name, CommandHandler handler) Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.axonframework.messaging.commandhandling.CommandHandlerRegistry
subscribe, subscribe
-
Constructor Details
-
DistributedCommandBus
public DistributedCommandBus(@Nonnull CommandBus localSegment, @Nonnull CommandBusConnector connector, @Nonnull DistributedCommandBusConfiguration configuration) Constructs aDistributedCommandBususing the givenlocalSegmentforsubscribinghandlers and the givenconnectorto dispatch commands and replies to different segments of theCommandBus.- Parameters:
localSegment- The localSegmentCommandBusused to subscribe handlers to.connector- TheConnectorto dispatch commands or replies.configuration- TheDistributedCommandBusConfigurationcontaining the load factor and theExecutorServiceFactoryfor this bus.
-
-
Method Details
-
subscribe
public DistributedCommandBus subscribe(@Nonnull QualifiedName name, @Nonnull CommandHandler handler) Description copied from interface:CommandHandlerRegistrySubscribe the givenhandlerforcommandsof the givenname.If a subscription already exists for the
name, the behavior is undefined. Implementations may throw an exception to refuse duplicate subscription or alternatively decide whether the existing or newhandlergets the subscription.- Specified by:
subscribein interfaceCommandHandlerRegistry<CommandBus>- Parameters:
name- The name the givencommandHandlercan handle.handler- The handler instance that handlescommandsfor the given name.- Returns:
- This registry for fluent interfacing.
-
dispatch
public CompletableFuture<CommandResultMessage> dispatch(@Nonnull CommandMessage command, @Nullable ProcessingContext processingContext) Description copied from interface:CommandBusDispatch the givencommandto thecommand handlersubscribedto the givencommand's name. The name is typically deferred from theMessage.type(), which contains aMessageType.qualifiedName().- Specified by:
dispatchin interfaceCommandBus- Parameters:
command- The command to dispatch.processingContext- The processing context under which the command is being published (can benull).- Returns:
- The
CompletableFutureproviding the result of the command, once finished.
-
describeTo
Description copied from interface:DescribableComponentDescribe the properties ofthis DescribableComponentwith the givendescriptor.Components should call the appropriate
describePropertymethods on the descriptor to register their properties. The descriptor is responsible for determining how these properties are formatted and structured in the final output.Best Practices: As a general rule, all relevant fields of a
DescribableComponentimplementation should be described in this method. However, developers have discretion to include only the fields that make sense in the context. Not every field may be meaningful for description purposes, especially internal implementation details. Furthermore, components might want to expose different information based on their current state. The final decision on what properties to include lies with the person implementing thedescribeTomethod, who should focus on providing information that is useful for understanding the component's configuration and state.Example implementation:
public void describeTo(ComponentDescriptor descriptor) { descriptor.describeProperty("name", this.name); descriptor.describeProperty("enabled", this.enabled); descriptor.describeProperty("configuration", this.configuration); // A nested component descriptor.describeProperty("handlers", this.eventHandlers); // A collection }- Specified by:
describeToin interfaceDescribableComponent- Parameters:
descriptor- The component descriptor to describethis DescribableComponentn its properties in.
-