title: Why use ASP.Net Web Api instead SignalR for internal project
body: <p>I know, ASP.NET Web API is designed for creating restful APIS, while SignalR is for realtime communication. So they are not competing technologies.</p>
  
  <p>Imagine this: you are creating a client/server application, you are writing a desktop client that will be connect to a server to run some actions. The actions are started by the client, not by the server so both of them work.</p>
  
  <p>If this is a Internal application, and you are not exposing the API, why would you use Asp.Net Web Api instead SignalR?</p>
  
  <p>In both you have methods in the server that will run when the client call them. In Web Api as actions in the controllers, in signal R in the hubs. Both allow you to send parameters to the methods, and get the result in the client.</p>
  
  <p>Knowing that traffic in SignalR is a little bit lower than in a Web Api (because in websocket the HTTP connection is established permanently and not create for each request), I would go for SignalR. Am I missing something?</p>