CODEWITHSUNDEEP
c#wpfwinformsservicearchitecture
Web Dev
Web Dev

Reputation: 2937

Client App vs Windows Service vs?

I am currently looking into some re-architecture for a set of applications for our organization. We currently have a set of 10-15 odd stand-alone applications that communicate to each other and provide an intermediate level between client software and hardware.

Problem with current model is lots of individual apps, which add memory overhead, latency in communication, bloat the system and make it difficult to recover from issues in case of any of these apps crashing.

I am thinking of combining the application into 1-2 logical units that help address some of these issues. The dilemma is on how to do this well:

The goal is to have an always on system that will handle all of the client-hardware comms but also have a rich admin-user configuration UI that will be able to talk to all of the individual components of this system and provide config/etc capabilities. Having a WinForms/WPF application will allow easy admin-user access to the system config and provide real time feedback (camera feed, etc), but will leave this open to admins accidentally closing the window. Having a service doing all of that work is great, but I am not sure on how to provide a rich admin-user UI that interacts and changes this service.

Any ideas or links worth reading?

Thanks!

Upvotes: 3

Views: 415

Answers (1)

Web Dev
Web Dev

Reputation: 2937

just thought I'd update my own question for anyone else that might be having a similar question.

What I went with is a centralized Windows Service that exposes a number of WCF endpoints for a number of its child components. Sitting on top of that is a UI application that communicates to the Windows Service through the WCF endpoints. To make building & debugging easier the Windows Service is configured to run as a Console application when run in debug.

This solution seems to work great so far!

Upvotes: 1

Related Questions