title: Simple lightweight service layer
body: <p>I need to expose some logic locally as a service…</p>
  
  <p>The objects sent/received to/from the logic are quite large, the information is sensitive and the logic will never need to be exposed externally it is for use on the local server only.</p>
  
  <p>Some MVC developers are argueing that it should be exposed using a WEB Api service – is it worthwhile implementing this?</p>
  
  <p>Their argument is that with Web API it is much more integrated into MVC and makes displaying result much easier (I know nothing about this side of things), my fear is that we will have to implement complicated authorisation and sacrifice performance.</p>
  
  <p>Is there no better lightweight service layer that fits this scenario? WCF named pipes seems logical to me, or just reference it as a class library - yes the config files are a pain but not the end of the world. Basically we just want to serve up some logic locally.</p>