Any patterns for high availability Windows service?

Question

Situation

I have a Windows service that I would like to make very affordable.

I have two non-clustered servers (standard version of Windows Server 2003).

Question:

What parameters should I make so that my service is automatically available?

I can recall the option of an asymmetric master-slave , which is to support the work running on both machines with a heartbeat message between them, so one acts as a master and the slave automatically takes itself when the master does not respond.

Do you know any other ways to implement this?

note: Please do not give me this answer , I DO NOT / will not / cannot have clusters.

Answer 1

If you are in a Windows service, you have a web / wcf service, you can configure your client to the primary URL of the service and the URL of the secondary service. Then you can change the client’s connection logic to use the secondary service when the connection to the main service fails.

You can do this transparently by adding a router service that will follow the above logic. Basically, proxying operations for any service to which it is connected. But this adds another point of failure, the router service.

, , - Windows. - http://code.google.com/p/daemoniq/wiki/WindowsServiceRecoveryOptions

Answer 2

MS, ( http://msdn.microsoft.com/en-us/library/ms998414.aspx)