The reason on-premise program was postponed is some dependencies
such as Service Bus for Windows (on-prem version of Azure Service
Bus) which is really hard to deploy, maintain and support. Because
of that the whole product installation is not so flawless. Also
Service Bus crashes on machines with .NET 4.6 installed and looks
like Microsoft stopped it's development/support.
So, our next step in order to make it happen again is replacing
SB with alternative queuing engine. RabbitMQ is the most promising
candidate right now. You can recommend something else.
on 05 Oct, 2015 03:27 PM
For alternatives, there are more "simplistic" approaches such as
ZeroMQ, Redis and SQL Service Broker.
But for something with similar capabilities, RabbitMQ is a
pretty good choice and actually fairly easy to get up and going
I have a theory that Microsoft's continued push of BizTalk as an
ESB solution (it isn't, but BizTalk is the continual solution
looking for a problem) is one reason why Service Bus for Windows
has languished. But the most compelling reason being that the
underlying Azure infrastructure just isn't there for a typical
Windows install (Like Azure Queues).