if you are looking for performance, static language files sourcing is the best approach.
if you are looking for ease of manipulation, and editing, you need a dynamic storage, a key value store in memory would be a good alternative than traditional relational databases.
If i was in yuour shoe i'd use both, i'd use Database for the texts that are used more than once as changing the text in this case would be easier you'll have to change on one place only, and use a resource file for the texts used only in specific cases as depending totally on DB would slow down the process, for generic texts use DB and cache these texts to reduce number of hits on DB.
Many people use the two terms “web design” and “web development” interchangeably, but they really do have two different meanings. If you’re looking for a new job or someone to build your website, you need to know the difference.
Web Design
Web design is the customer-facing part of the website. A web designer is concerned with how a site looks and how the customers interact with it. Good web designers know how to put together the principles of design to create a site that looks great. They also understand about usability and how to create a site that customers want to navigate around in because it’s so easy to do.
Web Development
Web development is the back-end of the website, the programming and interactions on the pages. A web developer focuses on how a site works and how the customers get things done on it. Good web developers know how to program CGI and scripts like PHP. They understand about how web forms work and can keep a site running effectively.
I think you should go with resource Files. Because ASP.NET and the .NET framework ship with support for multilingual applications, namely in the form of Resource Files, the CultureInfo class, and the System.Globalization and System.Resources.ResourceManager namespaces.
Some of the key highlights are:1. Content is separated into simple XML files2. There's a separate XML file for each supported language3. The code to load values is relatively simple and short4. The ResourceManager class automatically retrieves the content from the right XML file based on the thread's CurrentCulture value5. You can easily have1 actual page, for N supported languages.6. response time is fast, etc.
please refer this article to design multilungal websites:
http://www.codeproject.com/Articles/7998/Creating-multilingual-websites-Part-1
Hope you find the answer helpful
It depends on what you are planning to create.
If your web application is serving content that users can't edit, then you should use localized resource files.
If your web application resembles some kind of content management systems, then you should use a dynamic store (usually database).
You may need to use them both: Localized resource files for static content (labels, table headers, email templates,…), and database for the content that users can add or edit.
I agree with Hamzeh and Nour.
If you have static content and want to be served fast it will be better to use resources files, also that for text that used once or in some certain places only in the website.
As for dynamic content that changed and editable you will need to use database.