Provide a Service Bus emulator on a local computer
Providing a Service Bus emulator on a local computer will reduce development costs.
Thanks for this valuable suggestion. We are always working to provide a good developer experience including visual studio tooling to create/update queues etc. We do provide Service Bus on-premise as a developer scenario (this can be run against SQL express as well as on client OS). While not light-weight as an emulator it does provide full symmetric functionality and allows users to use the same messaging features etc. It is a lot of additional cost to provide an emulator when we already provide a full feature on-premise offering that is free of cost. Would like to hear if you have concerns to this approach.
Since the On prem SB is dead, Can we please reopen this issue ?
Lyle Thompson commented
So no more voting on this issue? Is it just a pipe dream?
Wow.. 2019 and this is still not solved!
Florencia, Christopher (MBMXC is) commented
This is awful, we need a non connected option for developers and don't have crashes when 2 access the same bus. If there are not an emulator, Is there a way so overload and custom some class to mock the service bus? Something class that works like proxy when a message is receive or sent?
George Young commented
Yes please, for QA for Dev and for Continuous Integration, having to manage and connect to multiple real Azure SB instances is a huge headache. Please give us a simpler way.
As a developer, I don't think MS understands. We are not talking about on on-premise service bus but a simple bus that runs locally when we are either not connected to the internet or on prem or when our connection is really slow and we would like to run locally. This can't be that hard to do, as you guys created MSMQ and then windows server service bus.
Please reopen this. This is a huge negative for Azure Service Bus
The response above from the Microsoft team is no longer valid.
So is there a change in stance on this now?
David Burg commented
+1 this is a significant impediment to developers of service bus clients. I see our engineers not doing any unit test at all because the cost is too high compared to other services client testing.
David Cloutier commented
Development scenarios would be greatly eased.
Please reopen and reconsider.
The answer provided is no longer valid, since the on-premise product is dead.
Hello, this issue needs to be reopened.
Please provide the right tools for Azure developement.
This should really be reopened
Matt Whetton commented
As mentioned below, the on-premises service bus is dead so this issue should surely be reopened
A Fanshawe commented
I like to test my code locally using functional tests written in cucumber, that treat the application as a black box.
Having an in-memory emulator would be great;
i.e for DB's I use https://en.wikipedia.org/wiki/HSQLDB,
for AmazonS3 I use https://github.com/findify/s3mock
For me I need it to work on a java JVM (1.8)
be started/stopped by the test, queried and drained by the test
used by the application as if it was the real instance.
With on-premises servicebus dead, could we please re-open this?
Ravi Chinni commented
Azure Service Bus SDK is far ahead compared to the Windows Service Bus. This causes problems. We have to downgrade to the nuget packages that are compatible with both on-prem and azure. There by loosing on the support for the latest.
So for a good developer experience a local emulator is a must.
We are hitting the same issue that Michael Yeaney mentioned below. We are a team of 10 developers working on Azure Service Bus based solution. Sharing the same ASB instance will lead to problems.
Eric Renken commented
For development I would love the emulator as part of the Azure Storage emulators. Not so much for costs but just easier to use and run. We have no on premise servers anymore and I am concerned what kind of resources a full blown Service Bus service would use on my development computer.
Mauricio Dominguez commented
The problem with Service Bus for Windows Server (which despite it's name can be installed on Windows 8+) is that it's cripplingly lagging when compared to the Azure Service Bus. i.e. Service Bus 1.1 (the latest version) only supports Azure SDK 2.1 and now we're at version 2.5, meaning the code can't seamlessly be used to test by a dev and then deployed
James D. Schwarzmeier commented
Thanks for the response. In my case, I make heavy use of the service relay feature. To my knowledge, the on-prem version of Service Bus does not support this functionality. Additionally, to echo Rhys's comments below, it is much more difficult to install and configure and has a number of pain points.