Compare to Azure Functions, that has a top-level documentation page on doing exactly this:īut there's nothing on the Azure Service Bus docs on local development.
#Docker masstransit .net how to
Unfortunately for us, there's not really any guidance on the Microsoft documents on how to do this. To develop effectively, we need figure out a strategy to ensure isolated developer environments.
I don't want one developer producing messages, and another developer consuming them, while the original developer is left waiting for those messages to arrive. This is especially problematic for stateful resources, where I have to worry about someone else changing the state I'm working with.īack to Azure Service Bus, what we don't want to happen is have multiple developers all reading and writing from the same queues. We can no longer reason about our code versus someone else's. When developers are forced to use shared resources, we introduce contention. This poses a challenge to the team - we want to ensure that environments are isolated from each other, and each developer's environment won't interfere with another's: Developer resources isolated Of all these, only the last one on the list can't be run external to Azure. This is a bit alien to most developers, as typically, we can run the entire production workload locally. For teams new to Azure Service Bus, one of the first questions you have to answer is "how do I develop against this?" And it turns out the answer isn't that straightforward - because it's currently impossible to run Azure Service Bus outside of Azure.
0 kommentar(er)
