I would like to know is it a good or a bad idea to store resources - localization strings - in a database?
I have a project, which is a two months old S#arp Architecture's v1.9 - based web portal. I store resources in a database.
I could have an empty database and if I call for a resources by name in my html the requested resource string will be dynamically created for all installed languages.
If user adds a new language via admin panel, all existing resources will be copied for this language. So administrator could change all necessary labels via sweet UI.
I want to move my project to Orchad because customer wants more features, which I will be implementing much longer than just use Orchad and migrate my existing business logic.
I know, there are resources editors for Orchad as modules, but just curious - is it worth adding, as an option, storing resource strings in a database?
Will this hit performance? It should not, because NHibernate caching (it has 2 levels of caching!) and my old web site's performance is really great! :) And we have 4 languages with ~ 1000 strings each.