Localization using database approach

We need a robust and efficient database model to store translated content in multiple languages.

 

Suppose we are asked to design a data model for a multilingual e-commerce application. We’d need to store text fields like product_name and the description of products in various languages. We’d also need to store text fields in other tables, such as the customer table, in all these languages.

 

To understand how to design our data model with content translation in mind, we’ll examine different approaches by using these two tables. Each of these approaches has pros and cons. The approaches demonstrated below can be extended to other tables in your data model. Of course, the exact approach you choose will be based on your own requirements.

 

1.Adding Separate Language Columns for Each Intended Field

2.Creating a Separate Table for Translated Text

3.A Translation Table with Rows for Each Language

4.Creating Entity Layers for Translated Fields and Non-Translated Fields