Rebus knows what queue to send it to based on the type of message I'm sending. Routing(r => r.TypeBased().Map(Configuration))Īlso in my Startup.Configure method I added the following call to UseRebus: () įinally, in my controller or Razor page that wants to send the message, I simply take a dependency on, and call the Send method. Transport(t => t.UseAzureStorageQueuesAsOneWa圜lient(storageAccount)) Logging(l => l.MicrosoftExtensionsLogging(provider.GetRequiredService())) Services.AddRebus((configure, provider) => configure var storageAccount = CloudStorageAccount.Parse(Configuration.GetConnectionString("AzureQueues"))
In my simple example I have one message called VoteMessage, and I'll send that to a queue name I read out of configuration. I need to pass in a CloudStorageAccount which in development can use the connection string of the Azure Storage Emulator ( UseDevelopmentStorage=true).Īnd I also need to tell it what queues to route different message types to. I'm using UseAzureStorageQueuesAsOneWa圜lient for the transport as this project will only need to send messages, rather than receive them. I'm configuring it to integrate with the ASP.NET Core logging. Next, in Startup.ConfigureServices we'll use the AddRebus method to set up Rebus. In the project that will send messages using Rebus, we'll add references to following NuGet packages in our csproj file:
MASSTRANSIT VS AKKA FREE
And of course by using an abstraction, we are free to change later to a different underlying transport.
I'm going to use Azure Storage Queues as the transport as they are (1) very simple and cheap, and (2) have an emulator you can use for local development. In this post, I'll go through the basics of setting up Rebus in ASP.NET Core, where we are going to have one microservice send a message, and another handle those messages. For example, in Azure you could use Azure Service Bus, Azure Storage Queues or Azure SQL Database, and many other "transports" are available. NET that allows you to plug in a few different services as a back-end. In my recent Pluralsight course " Versioning and Evolving Microservices with ASP.NET Core", I built my demos on top on an existing microservices application that had been created as the basis for a Microservices in ASP.NET Core learning path on Pluralsight (which is nearing completion).įor messaging between microservices, this application used Rebus which is a very simple service bus implementation in.
0 kommentar(er)
