I am developing an application and try to design it so that the WebAPI can be deployed on one server while the web application that consumes data through the WebAPI can be deployed on a different server. That means both of these items (WebAPI, Website) are separate projects. However, all example code I see always assumes that the WebAPI and Website are contained in one solution. That makes things like Globalization and early binding easy. For example for globalization I can just decorate my model class with Display attributes (in the WebAPI project) and then define additional resources for other languages (in the Website project). However, that seems to break down if these projects are completely separated.
That leads me to the question if it is unrealistic/overkill to design the app so that the WebAPI can be deployed on a different server than the website? Or is there an easy way to still make globalization, early binding, etc. possible? There is probably an easy solution but I could not find an answer to it yet.