From a scalability point of view is it advisable to have the ServiceStack API and MVC projects in separate projects. The solution overall is far more API heavy than web. Seems like a possible waste to scale option 1 below due to the bloat from the web element of it.
Just wondered if anybody had any thoughts on the following approaches:
Single Project - MVC/ServiceStack combo. All web and API call into single place - scale this.
2 Projects - MVC/ServiceStack combo -> service gateway -> Pure ServiceStack API project (Scale this API project which also services the web project)
Would be interest in peoples thoughts.