2
What would be the best strategy to internationalize a system in the DDD architecture, knowing that we have strings to internationalize present in the layers:
- Presentation - Views
- Application - Viewmodels nos Dataannotation
- Domain - Validation and Specifications
Taking into account that the Domain layer should not know any layer, it would be discarded the possibility of creating an internationalization project in a layer that permeates all others?
"would be ruled out the possibility of creating an internationalization project in one layer that permeates all others?" In my opinion, it would not be ruled out, this internationalization project is clearly a cross Cutting Concern.
– Marcell Alves
Ola Marcell! But what you tell me by the Domain layer is agnostic, that is, it does not depend on any other, even so you find it interesting to create a Crosscutting project, because then my domain would know this project.
– Wagner Santos
I hint at this framework, and how it handled localization: https://aspnetboilerplate.com/Pages/Documents/Localization Using IOC you can create a crosscutting layer with no direct relationship to Domain.
– gabrielbarceloscn