All geek questions in one place

What is the best way to communicate between programs in .NET and why?

Our company continues to discuss whether to use custom API libraries or create a web services farm so that our programs can transfer data between each other. For me, web services make the most sense in terms of compatibility and update flexibility, but I also heard some good reasons to use DLLs.

Is there a preference for .NET applications, or a choice that you find that works best? And if so, why?

Thanks!

+3
source share
9 answers

- .net-, , , dll. Remoting .

, / , API - RESTful .

, , .

, , - , , -, , , , - , .

+4

, , WCF. :

  • / . ?
  • . , WCF, . WCF - . , , , . xml . . WCF.
  • !!! !!
  • . WCF .

da-bomb, - , Security .., WS- *, . WCF. , , , -, Microsoft.

, WCF. , DLL.

+9

DLL . , dll . , Outlook, .

, , -.

, , , .

/-/Remoting/WCF, .

+5

, , , "" "". web- , , , , ( , - ).

+4

.net/MS -, microsoft .

, , - - - . , . .

SOA, .

+3

. - , , tcpchannel, . .

+2

, -/WCF, .NET TCP/IP-. , , ..NET remoting , - , codegen , .

+2
source

WCF is actually - the way here - write a service, let the configuration decide the transport medium.

In terms of vehicle selection, many of them are truly related to your network architecture and requirements. Http is great for remote things and going through firewalls, but bloody ones are ineffective, while Tcp can be fast but unreliable.

+2
source

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

More articles:


All Articles