Service Bus for Windows Server

Microsoft recently published Service Bus 1.0, which is free to use on Windows servers with the appropriate license, this makes Windows servers have features such as Windows azure message service.

Service Bus for Windows allows you to provide and operate Service Bus topics and service bus queues on any windows 2008 R2 and later servers ). The entire solution can be run on a single windows machine, or supports high-availability multi-node deployment models. In addition to the Windows operating system, the software also requires SQL Server 2008 R2 (and later) as the persistent layer and service management provided by Windows powershell.

In addition to Microsoft Active Directory, this product lacks any access control service components and Authentication Modules. Previously, Microsoft tried to establish a completely symmetric relationship between local and cloud products through "appfabric. However, the only product that is commonly used in two environments is the in-memory cache engine. The windows azure team recently discarded the appfabric product name. Microsoft seems to have selected the "Service Bus" name as evidence.

To use service bus 1.0 for development, read this msdn document. In addition, you can also refer to the cloudfx library, which abstracts some complex tasks of the Service Bus, such as message re-transmission.

In. net, besides service bus, there are other messaging service software, such as nservicebus, rhino service bus, and masstransit.

Sam vanhoutte, chief architect of IT service company codit, elaborated on a set of scenarios in a blog post. In these scenarios, using a self-managed environment is more suitable than using Microsoft's Windows azure cloud.

Scenarios where only persistent message transmission is required

If you only need to exchange messages locally, you can use the service bus for Windows Server to transmit messages between applications and services, and ensure the durability and reliability of message transmission.

Storage and forwarding scenarios

On the service bus for Windows server, you can define a subscription of the forwardto type on the topic, as long as the message matches these subscription rules, it will be automatically forwarded to the pre-defined message entity. Although forwardto cannot forward messages to a remote entity, there is a bypass solution to solve this problem, that is, to define a subscriber and let it listen to the local forwardto entity, then, the message is forwarded to the public entity.

Distributed scenarios

Most enterprises are composed of multiple business units or subsidiaries that need to be interconnected with each other. In many enterprises (often after mergers and acquisitions), different subsidiaries use different technologies. Therefore, using service bus as a message exchange gateway is a good choice. Each unit can use its own standard (rest, soap,. net, amqp ......) Interact with the gateway.

RelatedArticle:

Service Bus 1.0 installation instructions

Summary of Service Bus for Windows Server