Internationalization in Domain Driven Design (DDD)

Question

Internationalization in Domain Driven Design (DDD)

Navigation

#1 by (1 votes)
#2 by (0 votes)

2

What would be the best strategy to internationalize a system in the DDD architecture, knowing that we have strings to internationalize in the layers:

Presentation - Views

Application - ViewModels in DataAnnotation

Domain - Validation and Specifications

Taking into consideration that the Domain layer should not know any layer, would it be ruled out the possibility of creating an internationalization project in one layer that permeates all the others?

c# ddd

asked by anonymous 31.03.2017 / 14:53

2 answers

Open ASP.NET project that is coming from another machine How to obey the Open / Closed principle in this situation?

score 1 · Answer 1

I think the best way is to use the Resource DLLs, one for each language you want, then only handle the calls to use the right culture, if it is Asp.NEt core, you have an example in the abiaxo link, ach is a very complete example:

link

score 0 · Answer 2

Hello friends, after investing some time in research, I solved my internationalization problem by creating a CrossCutting layer, where through the layers I internationalize my entire project, ie, I can internationalize my Views ), ViewModel (Application layer), validation messages, specifica - tions, etc. (Domain Layer).

Taking advantage of this, I created a tool that automates the whole process of creating the layers (except for my Views), based on queries in the database, that is, to perform a simple Crud in DDD, I have about 18 files where they are generated in just one click. I will in the future make it available to help the developer community