This document discusses different approaches for mapping objects to data transfer objects (DTOs) in domain-driven design (DDD) applications, including using EmitMapper, AutoMapper, and homegrown mapping methods. EmitMapper is fast but has low reliability, while AutoMapper is reliable but more object-oriented. Homegrown mapping depends on the implementation and can have high costs. The document also provides code samples for mapping between layers in DDD applications using these different mapping strategies.

1. © O LEKSII DUKHNO @ LO HIKA SYST EMS

2. COMPLEXITY OF SOFTWARE

3. ABSTRACTIONS AND MODEL

4. ABSTRACTIONS AND MODEL
Модель представ-ляет собой специально
отобранный и сознательно упрощенный запас
знаний (набор данных)
Представленный в структу-рированной форме.

5. DDD AS THE TOOL

6. DTO AND VIEW MODEL
DTO
• Model data only
View Model
• Model data and behavioral aspects

7. WHY USING O-2-O WITH DDD?
Layers are independent
Code aligning
Flattening logic encapsulation

8. RESULTS USING DDD WITH O-2-O ?
Neater code
Simpler support
Better understanding

9. SAMPLES - DATA LAYER

10. SAMPLES – SERVICE LAYER

11. SAMPLES – APPLICATION LAYER

12. MODELS, DATA TRANSFER OBJECTS AND VIEW MODELS

13. HOME-GROWN OVER “OPERATOR” KEYWORD
Code template:
• public static implicit operator DTO_Type ( Entity_Type entity)
Open sample

14. HOME-GROWN OVER EXTENSION METHODS
Code template:
• public static DTO_Type ToDTO ( this Entity_Type photo )
Open sample

15. HOME-GROWN OVER SEPARATE CLASS
Instructions:
• Define static or singleton class
• Implement conversion methods explicitly
Open sample

16. EMIT MAPPER KEY SUFFICIENCIES
Fast (close to hand written code)
Supports mono
Pretty extensible

17. EMIT OBJECT MAPPERS

18. EMIT MAPPERS FACTORY

19. EMIT MAPPER CONFIGURATION

20. EMIT MAPPER
Standard
Custom converter
Post processing
Custom configurator

21. OTIS
Metadata
Configuration file
Custom mapping
providers

22. OTIS
Metadata
No DateTime and nullable value types support
Configuration file
Custom mapping
providers

23. AUTOMAPPER
Mapping Mapping
Through Through Test Mapping
Convention Configuration
Source/Destination Projection Validate
Properties Names Configuratio
Convention Type n
Converter
Value
Resolver
Ignore

24. USING AUTOMAPPER IN THE ALLOCINE-CMS

25. USING AUTOMAPPER IN THE ALLOCINE-CMS

26. THE OTHERS OPTIONS
Entities to DTOs
T4 templates – To
be continued

27. MAPPERS SUMMARY TABLE
Style Facade Spee Open Reliabilit Silve Manuals Cost
/// d Sourc y rlight
e
Emit Procedura No The Yes Low Yes Poor Mid
Mapper l Best
Auto Object Yes Good Yes High Yes Good Low
Mapper Oriented
Home- Any Depends Depend Could Depends Yes Depends High
grown s be