We are currently using it for development, however the last release was Service Bus 1.1 over two years ago.
Should Service Bus for Windows Server be avoided?
Edit: It is officially dead. Microsoft "will not provide an immediate successor for the standalone Service Bus for Windows Server 1.1 product" and it "and will go out of mainstream support on January 9, 2018".
You may want to monitor this Stack Overflow Question (which points to this UserVoice idea) for updates on it being brought to Azure Stack so it can be used on-premise. The latest update from Microsoft was from Sept. 30, 2018 - "Thanks for your feedback. We are pleased to inform you that we are bringing Event Hubs to Azure Stack. We announced Private Preview at Ignite 2018... Service Bus will follow next." As of Dec 2019, Event Hubs is still listed as "IN DEVELOPMENT" on the Azure Stack key capabilities site.
Original answer (Aug 4 '16):
The short answer: Service Bus for Windows Server does have a future as part of Azure Stack but it is not going to be free and will not happen this year (2016).
Apparently the roadmap was announced on May 12 at Integrate 2016 during Clemens Vasters's Service Bus – Roadmap, What’s next? talk. You can listen to the announcements related to Service Bus at about 40:35.
Interesting quotes from the video:
SB for Windows Server was built for - was primarily motivated by Sharepiont and workflow.
We [Microsoft] are very surprised by the success of it because we kept it super quiet. It is growing like crazy. We are not going to strand you.
The Microsoft Azure Stack is the way forward to take the cloud on-premises.
Service Bus is a better product than any of existing message brokers - even the ones you pay $4 million for.
It is the only 5-way, parallel load, multi-node broker that you can install locally that does all the fail-over and you can set up and it just works - backed by SQL.
Service Bus and Event Hubs will be hosted by Azure Stack and run on top of it. But the timeline is not in this year (2016).
What happens with MSMQ? We are just thinking about that now. We might go and have a version of Service Bus that is shrunk and will also run outside of Azure Stack. So you could run standalone or on-premises private cloud deployment or on the cloud. And the goal is all will be built and supported in a way so that we don't have the situation where we build something and have it sit there for 3 years.
The entirety of Azure is now committed to that on-premises platform which was not the case for Azure Pack.
We don't know what the price will be but we will most certainly be cheaper than IBM.
When we just put up one of the best message brokers in the world as a free download we made a huge mistake. This is because it is hard to commit resources within Microsoft to maintain a free product.
Thanks to user Arunkumar BizTalk360 for pointing us in the right direction in this Microsoft Azure thread
Turns out, it is dead now....
https://azure.microsoft.com/en-us/blog/collaboration-and-federation-azure-service-bus-messaging-on-premises-futures/
As a consequence, we are announcing today that we will not provide an immediate successor for the standalone Service Bus for Windows Server 1.1 product. Service Bus for Windows Server 1.1 was shipped as a free download that could be installed inside and outside of the Azure Stack precursor Azure Pack. The product is available as a free download and will go out of mainstream support on January 9, 2018, following the regular Microsoft lifecycle policy as published at the initial product release.
It is not dead. It is a fully supported add-on to Windows Server 2012 R2. A roadmap for the way forwward will be announced later this year.
It's kinda dead.
Mainstream support ended 1/9/2018. Extended support will end 1/10/2023.
So if you are running the service bus and do want to keep running your bus on premise and not in a cloud you have a little less 4 years from now to find and deploy a replacement.
Related
I'd like to create a simple server service that can perform the following tasks:
Retrieve presence info for specified user(s).
Send message to specified user.
From what i've been reading, and because i'm siting server side I could choose to use UCMA 5.0? But i'm seeing a lot of push of the new UCWA SDK and working with the UCWA rest services. Is there any particular reason why i would use UCWA server side rather than just the UCMA API? I read that UCWA will, in the future, be support by Microsoft for Cloud --- Any input and experiences shared on this would be great.
Thanks, mike
UCWA will be at some point be supported in Office 365 indeed. So if you create an application with UCWA you can expect it will run in the next future on your S4B On-Prem as well as on Office 365.
I have to say anyway this support for UCWA on 365 is already long awaited, and still there's no official announcement about availability date.
A very good reason to choose UCWA instead of UCMA, also in case of server automation, is the much simpler deployment of UCWA (UCMA deployment is quite tough).
UCMA must run on a Windows Server OS which joins the S4B farm basically (thus sits in your DMZ)
UCWA can run on any device that 'speaks' HTTP. Your UCWA App can run, for instance, on a Raspberry Pi
I think this is a huge difference, for sure it is for your system administrator
Old thread, but in my experience, writing server-side code with UCMA is somewhat easier than trying to use UCWA - and all that UCWA really is is a UCMA application sitting on your Lync/S4B server with a REST wrapper.
For the fairly simple use-case you've described, you could write the service as a client-endpoint UCMA application, which avoids the rather irritating Lync/S4B topology changes and deployment headaches that Massimo alludes to for a TrustedApplication. In this configuration, you are essentially just a third-party client, and you provide the credentials to sign into Lync/S4B as a specified user. Under this scenario, the only requirements are that the server running your application needs to be joined to your domain, run a 64-bit Windows OS, and have the UCMA runtime installed.
Some sort of API support for Skype for Business on Office365 is badly needed. There was some promises of a UCMA-like SDK for Office 365, but it has been more than six months with no hints of an actual release.
Azure and EC2 are optimized for running servers. Lots and lots of servers. Both platforms attempt to manage tons of things for you -- in Azure's case, it wants to manage even the target operating system.
However, I'd like to use such a service for a different reason: Testing.
I've got a ton of operating systems I need to support. My tests don't actually take that long, but running them on every platform is time consuming. I was going to just use a cloud service for this, thinking that these machines would be running for much less than an hour, and it wouldn't cost all that much.
The problem is that the major cloud services won't run client versions of Windows -- Windows Server only.
Is there a cloud service which would let me run every client and server version, and every service pack level, of Windows released starting with Windows 2000 SP4 to the present day?
Try CloudSigma, Defiantly can upload your own ISO's and run any x86 and 64bit OS you like on it. They have their in-house versions to get started but you can bring your own OS versions.
Based in Switzerland but they would have also the servers in the US, performance i've expected to quite good.
https://www.cloudsigma.com/
There is also a free trail on at the moment
https://cs.cloudsigma.com/accounts/signup/
The list of Open Virtualization Alliance members may have some candidates for you.
A search on the page for "operating system" suggests the following possibilities (in addition to the already-mentioned CloudSigma):
ElasticHosts
stepping stone GmbH (I'm less sure about this one)
Sublime IP
No, commercial cloud services like Azure and Amazon EC2 are themselves virtual, so you don't get a great deal of control over the operating system.
An option may be to consider renting a full physical server (colocated, or managed) and then use a battery of virtual machines to run the tests. Something like VMWare's snapshot feature sounds perfect: spin up a clean virtual machine, deploy the test code, then throw away changes to the disk once the tests have been completed.
Or, indeed, as #Stuart suggests - run the tests locally.
This definitely isn't something Azure offers - I think all of Azure's images are based near to Windows Server 2008 R2.
For EC2 you could set up images for Server 2003 through to 2008R2 - but nothing else. There are also some services out there to assist with this - e.g. VaasNet http://www.vaasnet.com/catalog
For testing the other Windows operating systems, I simply don't think there's a cloud service available to let you do this. I don't even think there are any cloud services where you can run "Virtual PC" type applications on top of the hosted operating system - as I think most of the virtualization APIs are disabled in the cloud environments (virtualization within virtualization not supported!)
Sorry to say this, but your best bet may be local test hardware running VirtualPC images.
It appears that the Xen Cloud Platform might do what you're after. This page ends with:
Guest Operating Systems: the XCP binary distribution is delivered with a wide range of Linux and Widnows guests. Check out the release notes for a complete list.
And their PDF document Xen Cloud Platform Virtual Machine Installation Guide (Release 0.1, Published October 2009) says that Windows 2000 Server has "No known issues."
(I don't have any affiliation with Xen)
In conjunction with the above, there is also a list of Xen VirtualPrivateServerProviders, several of which say they include Windows.
Buy time on an EC2 instance and use it to host VirtualBox VMs with VMs set up for each operating system you want to test for. Use a RDP client or VNC or some other means to control the guest OS. This forum post seems to point to that being possible. But yes it is not a cloud service itself and you would have todo some initial setup and configuration work yourself.
we are currently on windows server 2008 R2, IIS 7.5 and we are going to open some of our data via WCF services.
To do that, we are planing to host our services on IIS but I heard that it is not a good idea for WCF services.
The problem with the WAS is that it is general purpose hosting engine. it's actually unaware that it's actually hosting a WCF service or a website (as far as I know)
I heard that we can install an extension to the WAS called the Windows Server AppFabric.
does anybody have any experience on
AppFabric?
should my app have to use so called
'Service Bus' to use AppFabric?
should I go ahead and definitely
install it?
at most basic level, how and where
can I install it? does it require
any licence?
Thanks in advance.
I don't think IIS us a bad idea - many developers use IIS to host their WCF services. IMHO you'd only use what you need, so if all you need is a hosting framework, then IIS is a very good option for WCF services. It is (almost) unaware that it's hosting a WCF service, but that in the majority of the cases isn't an issue.
Windows Server AppFabric as it's currently released provides three capabilities: a distributed caching system (so if you need to scale out your service you can use this cache to share state among the nodes); a packaging / deployment interface (in which you can package a project and deploy it a little easier in IIS); and a management / monitoring interface (where you can monitor the instances of WCF and Workflow services which are running in your machine).
Answers to your questions:
Yes, some people have experience with it :)
No, the application doesn't have to use it. You'd only use the ServiceBus if you need its functionality (relay)
Only if you need it. If you don't need caching or the monitoring capabilities, for example, then I'd say you don't need it. I've found in the past that the least number of components I have in my system, the less likely it is to break.
Go to http://msdn.microsoft.com/en-us/windowsserver/ee695849.aspx. And AFAIK you don't need any license, but you can check on the download page to see if it has more information.
There is no real common reason why not to host a service in IIS/WAS.
If you want to absolutely, totally 100% make sure that your service is continuously running some process, such as a continuous loop or polling monitor, and if any interruption no matter how brief is a major issue, then you'd want to look at alternative hosts.
Win Server AppFabric is most useful for WF Service hosting and caching. Note however that Win Server AppFabric + Win Server Service Bus 1.0 represents the first steps in convergence between the Azure platform and the Windows Server private platform.... In other words, whichever of the two ways you choose, that's what is going to be earning your bread and butter in 5 years time.
This afternoon, I used python script to test the performance of Redis on Windows.
It worked normally when the number of threads was only 10, but some exceptions occured when the number of threads reached 100.
Exception message:
3 [main] redis-server 1448
_cygtls::handle_exceptions: Exception: STATUS_A CCESS_VIOLATION 1394 [main]
redis-server 1448 open_stackdumpfile:
Dumping stack trace to redi
s-server.exe.stackdump
Is Redis stable on Windows?
Redis is not officially supported on Windows. Some unofficial ports exist (such as the one you're using), but I believe stability is not guaranteed for these ports.
Redis prime dev Salvatore Sanfilippo ('antirez'), December 2011:
I don't think Redis running under win32 is a very important feature. It is cool to have a win32 port that can be used for testing, as we had before, and as we have in a different implementation thanks to the Microsoft patch, so developers using Windows can easily test Redis and develop their projects. But what is the point in providing a production quality win32 port?
Regardless, parties within Microsoft are still improving the Windows build
Here’s to the first release from MS Open Tech: Redis on Windows
Claudio Caldato 26 Apr 2012 12:01 PM 8
We consider this not to be production ready code, but a solid code base to be shared with the community to solicit feedback: as such, while we pursue stabilization, we are keeping the older version as default/stable on the GitHub repository. To try out the new code, please go to the bksavecow branch.
The Redis download page now says "The Redis project does not directly support win32/win64, however we look at interest to projects trying to make a win32/win64 port that is separated from the main project...Currently both ports are not production quality but can be used for development purposes..."
We maintain a stable and production ready Windows port (native!) of Redis.
The Developer Edition is free.
Check out Memurai.
see:
Redis on Windows stable and reliable
I use it in my projects till last month and didn't experience any problems yet.
Announced today at PDC. Initially made up of a Service Bus, the Workflow Service, and the Access Control Service. What are they? Why would I use them?
I've looked at it a little. There's a few posts that convey a lot of meaning, I feel. This new wave of technologies really does look as 'big as NT' as is being reported in some circles.
In it's simplest form, map the current Microsoft server services for such solutions and imagine them hosted on Microsoft's data centres. So we have
Biztalk service bus / services->
.Net Service Bus
Windows Workflow -> Workflow
Services
SQL Server -> SQL Services
Active Directory Service -> Access
Control Service
(NOTE: these are approximations to illustrate rather than direct mappings)
Now initially it's not that your current Biztalk wired code can move into the cloud directly, but service contracts are being made avialable to run your own code against Sql, say, running on Microsoft kit. (remember we're talking to the cloud so all APIs will naturally be exposed via web services).
So software is finally moving to a subscription model perhaps - whilst pricing is not available, it's being promoted as a Pay-As-You-Go scheme.
Official links:
- MSDN - Windows Azure
- VS 2008 Tools (includes project templates)
http://channel9.msdn.com/posts/Charles/John-Shewchuk-and-Dennis-Pilarinos-Inside-NET-Services/