Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • The WebAPI project is the service layer boundry. I could have implemented it as, for example, a windows service hosting a WCF service. but we don't need any queuing, duplexing, or complex security requirements. So I went with the WebAPI. Commented Jan 11, 2013 at 20:55
  • the WebApi and the mvc app sit on different boxes. Commented Jan 11, 2013 at 21:02
  • Fair enough. All I was getting a is you already have a service layer boundary, the Service project. The WebAPI is a great interface for external clients, but it's usually overkill for internal apps. Unless, of course, you need a physically distributed architecture, in which case having a web service layer may be worth the extra overhead. Commented Jan 11, 2013 at 21:17
  • Its a legitimate concern Commented Jan 11, 2013 at 21:18
  • Agreed. It just wasn't mentioned in your original question. Perhaps you could add it to clarify? Commented Jan 11, 2013 at 21:19