High Availability and Scalability

Database mirroring: Database mirroring is a new high-availability feature in SQL Server 2005. With database mirroring, you can mirror a SQL Server 2005 database between two server instances. One database acts as the principal, and the other database acts as the mirror. When you use Service Broker, you can also mirror your Service Broker service between two databases, and Service Broker will ensure that your messages will be forwarded to the current principal.

Load balancing: Service Broker provides built-in functionality for load balancing. When you provide more than one route at the initaating service for a specific service name, then Service Broker randomly picks a route from the available ones and sends the conversation’s messages along this route. Therefore, load balancing is easy with Service Broker.

Message forwarding: Message forwarding allows an instance of SQL Server to accept messages from outside the instance and send those messages to a different instance. In this case, the instance acts as a Service Broker message forwarder. With message forwarding, you can encapsulate your physical Service Broker infrastructure and use message forwarding to scale things out.

Configuration notice service: An administrator typically configures Service Broker routing information. To provide dynamic routing information for your Service Broker application, you can use a configuration notice service. A configuration notice service exists on the initiating service side and provides dynamic routing information for a target service.