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.

3
  • thanks for the perspective. I hadn't considered the extra work being done by page construction, etc. However given that there is literally one razor view in the app and everything once bootstrapped is AngularJs, I'm not sure it's a concern in this case. Plus since the app is internal only, I don't think that security is too big a concern - bearing in mind that the back-end services which is where all data is really stored, will always be on separate boxes behind wcf services, with tons of security on them since these are used by the entire organisation. Commented Oct 10, 2015 at 23:39
  • Sure, your case is what your case is. I wonder if those services might be consumed by a different webapp in the future (or intended to be) and that's why its architected like it is. There again, the old architect might just have been looking down at it from 10,000 feet! Commented Oct 11, 2015 at 9:46
  • 1
    In our scenario we decided to develop Mobile app after the whole thing had been in production for a while. We were happy to have API server separated from UI server, because Mobile app had nothing to do with Web app. We could scale the 'mobile' and 'web' parts separately. Another thing worth to notice: Web app is really a just a fron-end/client, that means that Web app client (browser) calls API server to get data (in our case this is possible). The "redundant" HTTP calls between API and UI servers were negligible comparing to traffic between browser/mobile and API server. Commented May 17, 2017 at 10:53