Type of server application hosted on Windows Server

Question

.NET

Hello!

I'm wondering what is the right approach to develop server software hosted on Windows Server. Most of the servers that work and are developed in our company are console applications. Servers process incoming connections (socket, wcf), work with the database. Almost all have some kind of information output in the console, so you can always keep an eye on the health of a particular instance.

But I still think this approach is wrong. Dozens of icons in the taskbar, difficult to find the right instance (especially if something has crashed), the impossibility of centralized monitoring and management, problematic restart after a crash. In general, there are many shortcomings.

That's why the question is. Is there a standard approach to developing server software for WinServer? How should it look? How to monitor? How to start?

Windows Services comes to mind, centralized management software that connects to each server ... Maybe there are ready-made solutions?

Answer 1

Set up a normal ready-made monitoring system - zabiks, nagios, isinga, native from ms - configmgr, and finally you will be happy.
Well, or find any other monitoring, since only lazy people do not write them now.
Well, in general, I am now actively studying C #, including writing for the web, and there is a desire a little later to write my own monitoring system for MS products for some reason.

Answer 2

Well, firstly, there are several options for “hosting” the application: WAS (http://en.wikipedia.org/wiki/Windows_Activation_Services), Windows Service, Web Application (IIS) and on top of IIS there is AppFabric.
This is for launch. As for monitoring, Performance Counters (http://msdn.microsoft.com/ru-RU/library/windows/desktop/aa373083%28v=vs.85%29.aspx) and the monitoring service on the advice of foxmuldercp.
You can write management yourself. Through the web interface or through the console (PowerShell + .NET Remoting to the rescue)

Answer 3

wcf can be hosted in IIS for example. And yes, services. What kind of “central management software” do you need? Restart service on ten machines?