Build Clean Messaging in .NET with MassTransit

Awesome video! So many details covered, including switching transports, the difference between IPublishEndpoint and IBus, ensuring contracts are in a namespace, and changing brokers – really amazing. Fantastic work, thanks for the great content!

Hi, Nick, from the video, it has 1 publisher which published 1 topic and then consumed by 1 consumer only. Would like to know how two consumers consume the same topic. I tried but it seems like after the 1st consumer consumed the topic, the topic will be closed and the 2nd consumer unable to consume. Appreciate if you can demo about that two consumers consume the topic successfully

Thanks for this video. What about performances of MassTransit compared to dedicated ones? :)

Would love to hear your take on Sagas be it on here or dometrain

Resilience has been a hot topic at our workplace. I'd love to see more videos on that.

What is the benefit of this over grpc or websocket?

Yes, please do some Saga state machine content. It would be nice to have your take on that. Chris’ videos are good but I think the community will love to see you explaining things.

Awesome content, Nick! A sagas video would be nice. Also, what do you think about showing us how to add a unit of work with mass transit? Thanks

MassTransit has a transactional outbox as well.

Please make a video about Sagas =)

Does MassTransit allow real-time control of the banding?

This guy rocks! Thank you for the great video. Loads of details, so clearly explained.

If you speak 10% faster - you'll sound 10% more smart, speed it up! :)

sorry Chris! I like Nick's content more. Love MT but Your vids are difficult to follow 😂

thoughts on Rebus? I have nothing but the highest praise for it.

Another request for routing slips / sagas.

Saga related video would be highly appreciated 😀

The "well documented" in the intro. Man... You gotta be kidding me!
Just stumbled on this video after spending a couple of hours of reading the source code because I could not find anything useful in the docs.

It's a very useful library for sure and hats off to its creator and maintainers, but it has a lot of work to do on the documentation side.

That would be great to learn more about the sagas!

Nick, you are amazing and everyone thinks I'm a genius because I watch your videos. I have an app that writes to a DB however, the DB it taken down a number of times a month for maintenance. I was thinking of adding an internal que for resilience. Is that the correct answer?

Is it possible to set this up using IFunctionsHostBuilder in an Azure function app? I don't get any compile time errors, but when I run it it breaks on the 'AddMassTransit' section with an error saying 'Method SerializeObject in type MassTransit.Serialization.SystemTextJsonMessageSerializer does not have an implementation'.

Hello Nick, I need to ask you an question . If I use that this type to message among our service in windows 10 operation system that Won't I need any docker images etc...

Hello Nick, did you already looked at Dapr ? If so, what are your thoughts?

Tnx Nick
Please create a complete tutorial on implementing saga pattern using masstransit

The most important is where you publish the message to the subscribers but subscribers have their own queue to intercept the messages even if they are down. The introduction video did not have this case so I skip watching it this time round.

Great video Nick!, Very interested in a saga walkthru in MassTransit on YT or Dometrain

I wanted a video like that Nick. I am using MassTransit for the last couple of years at work and I wanted an easy way to explain it to the new developers. Now your video will help with that :)

This library is almost too good to be true. Thanks for the tutorial!

Assuming we have RabbitMQ transit, one consumer uses MassTransit, one publisher does not use MT, or reverse, how can they communicate with each other?

Awesome video, thank you!
Can you make video for more advance feature like consuming messages in multiple instances using round-robin and how handle in case of one instance failed to process the message after consuming (retries, redelivery to next instance) ?

Too fast and unclear explanations.

Yes to Sagas and Resilience!

Rebus enters chat

Will the sqs be created automatically if we run publisher first?

Definitely interested in more on masstransit, with sagas, statemachines, handling transactions etc, would even buy a course on it, along with many other more in-depth topics used for more complex enterprise/microservice solutions.

@Nick Lots of stuff to parse in here.

A few questions. What what you showed the same if there is a single consumer or multiple consumers? If multiple, which consumer is responsible for removing the message from the queue?

Also, is it a common best practice to have a single queue for message type? At our shop, it seems more common to have one queue and multiple message types go through the queue.

Also, I'd love to see some explanation of when to use SNS vs SQS and when and why to use them together.

Yes please, make more videos 😎

It would be perfect to know sagas concepts!

Not sure if it was intentional but you explained things well enough for dummies like me to understand the basics this time around and I appreciate that!! lol

Μπράβο Nick, thank you for this video !

a series about contract testing would be cool

Hey nick, can you talk about Task.Yield?

please do sagas

Hi Nick. Thank you for the video. I am not so familiar with AWS, but with Azure. In Azure service bus there is an option to create a filters on the topic by subscription. May you know if masstransit supports it? It would be cool if you could make a video about it. Thank you.

I love masstransit but I prefer to use Bustr because it is an abstraction on top of it to make it simpler to scale and more organized

I've been looking at MassTransit for a while for a rewrite of our code base and would love to see a series on it.

Only thing missing in MT are some simpler transports. Rebus has DB transport, even file system transport. It would allow for a single proces to have persistent messages without a broker (not everything runs in a cloud :)). Still, great library, with decent testing capabillities.

You should cover both sagas and testing in MT next :)

Yes please! Sagas!

Mass transit testing pls