The title is a little misleading. I have to build a new Web API application to service a bunch of different clients that we are also building. I don't need the parameters or the routes in the API localized.
Basically the clients will ask for a resource in a specified language and the web api will return the results.
My only requirement is that the localization resources will be stored in a SQL DB and not resource files.
Being that the Web API is only returning localized results and it doesn't need to be localized, should I try to be following .NET localization practices or should I just create a simple, cached table lookup function mimicking localization routines?