Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Generic Message Receiver
See original GitHub issueA simple way to use MassTransit to dispatch messages, without having to build a transport.
Similar to what was done to support Azure Functions, but not specific to any transport.
The generic receiver would be able to accept a real MassTransit message, or plain old JSON, or any type that has already been deserialized (think, <T>), and dispatch it through the MassTransit consumer pipeline.
Some basic extensibility points should be available, including a Publish and Send abstraction, that could be connected to anything (or nothing).
- Multiple overloads for message delivery
- JSON message envelope (MassTransit)
- JSON, raw, with message type overload
-
<T>, an already deserialized message type
- Exceptions should be propagated all the way up to the receiver’s caller, so that they can be handled by the calling function.
- Publish abstraction, callback style for published messages
- Send abstraction, callback style for sent messages (how do we get an address?)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m considering native support for Google Pub/Sub, I just haven’t dug into the API specification yet. Also, need to add support for GPB (and ultimately Avro). But that’s a v6.1 thing.
Watching this issue. Would like to see if I could make an attempt to wire up MT to Google Cloud Pub/Sub, this seems like a good start.