This policy is in place to avoid bugs being drowned out in a pile of sensible suggestions for futureĮnhancements and calls for help from people who forget to check back if they get it and so on. Issues are not the place for questions, and will either be converted to a discussion or closed.
Use GitHub Discussions to ask questions, bring up ideas, or other general items. The configuration for MultiBus is documented, and requires additional buses to define an interface (such as ISecondBus) and use the generic overloaded AddMassTransitPlease do not open an issue on GitHub, unless you have spotted an actual bug in MassTransit. Get help live at the MassTransit Discord server. This configures the container so that there is an additional bus, using RabbitMQ, with a single consumer AllocateInventor圜onsumer, using automatic endpoint configuration.
Get started by reading through the documentation. In this episode, the new features and fixes in MassTransit v6.3 are shared, along with a detailed review and demo of the new MultiBus feature, allowing multiple bus instances in a single dependency. I have never used XUnit, nor that specific package. Using that interface, configure the additional bus using the AddMassTransitFor all other cases, you don't really need MultiBus. MassTransit makes it easy to create applications and services that leverage message-based, loosely-coupled asynchronous communication for higher availability, reliability, and scalability. The main use case for MultiBus is when one application connects to two different broker instances, or even uses different transports. MassTransit is a free, open-source distributed application framework for.
0 kommentar(er)
