Is your feature request related to a problem? Please describe.
With Mass Transit going commercial, some engineers may want to switch to Brighter. Based on our conversations, it is likely that this would be an app-by-app approach, meaning we would coexist with Mass Transit in the ecosystem for some time.
Describe the solution you'd like
The main issue for interop with Mass Transit is mapping. We should provide:
- A default message mapper that maps to and from the Mass Transit format
- Transform pipeline middleware that allows an existing message mapper to be attributed so that we convert the output of that mapping to and from the Mass Transit format
- A how-to guide for moving from Mass Transit to Brighter. We should optimize the instructions for usage with an LLM to help folks using an LLM to convert.
Additional context
We may consider the same pattern for other libraries that are out there: JustSaying, Wolverine, Rebus, and Dapr in the dotnet space, and even Spring and Quarkus in the Java space. (Some of the Dapr work will need to be behind the support for heterogeneous channels that use the Cloud Events type for the channel type).
Is your feature request related to a problem? Please describe.
With Mass Transit going commercial, some engineers may want to switch to Brighter. Based on our conversations, it is likely that this would be an app-by-app approach, meaning we would coexist with Mass Transit in the ecosystem for some time.
Describe the solution you'd like
The main issue for interop with Mass Transit is mapping. We should provide:
Additional context
We may consider the same pattern for other libraries that are out there: JustSaying, Wolverine, Rebus, and Dapr in the dotnet space, and even Spring and Quarkus in the Java space. (Some of the Dapr work will need to be behind the support for heterogeneous channels that use the Cloud Events type for the channel type).