Single Page Application Server Separation of Concern
===

Im just in the process of putting together the base framework for a multi-tenant enterprise system.

The client-side will be a asp.net mvc webpage talking to the database through the asp.net web api through ajax.

My question really resides around scalability. Should I seperate the client from the server? i.e. Client-side/frontend code/view in one project and webapi in another seperate project server.
Therefore if one server begins (server A) to peak out with load/size than all need to do is create another server instance (server B) and all new customers will point to the webapi's on server B.

Or should it be all integrated as one project and scale out the sql server side of things as load increase (dynamic cloud scaling)?

Need some advice before throwing our hats into the ring.

Thanks in advance