All geek questions in one place

.net

I'm currently trying to create an application, and I am having problems choosing the architecture used for it.

This will be a .net application, and, in essence, this application will be a server on which certain software runs with which this application will interact. A support service should be running on this server, which will actually interact with this application, queue requests, etc. Then there will be a web interface that provides a user interface and communicates with a service that then communicates with the software, hoping that makes sense. This will mean that the web interface can be installed on another machine for real software.

So what I'm trying to install:

  • What is best used on the server on which the application is running, a web service running in IIS or a Windows service.
  • If the provisioning service is a Windows service, what is the best way to use the asp.net web application to communicate with it.
  • Are there any patterns or architectures that deal with such settings.
+3
source share
4 answers

Some thoughts / answers:

  • If you use WCF, you can switch from hosting to IIS or Windows Service as you wish. (Just put your main code in a dll, and then write a very small shell or web project.)
  • WCF, . : TCP, HTTP/Web Services, IPC, .. , , .
  • , , WCF, , .
+4

, Windows, (API) WCF. , API - (SOAP) API REST. - , , (WCF, SOAP, REST) ​​ , . , WCF , , , .

, . n-. ( , ), .

+1

, Windows Communication Foundation, - / .

Windows Communication Foundation .NET Framework, - , .

+1

Windows, , ​​ iis .

mq (, MSMQ) - . MQ . ( ), .

- -, , , -, , - , .

, - push-, System.Net.Sockets WCF ( -), , , .

+1

Source: https://habr.com/ru/post/1715106/

More articles:


All Articles