Session
Identity Obsession: What is it and Why It Should Be Avoided
Identity Obsession is a code smell that can occur in the context of Domain-Driven Design where entity identities are misinterpreted as always being global identities. This session details how it can happen, how you can recognize it, and the issues that arise and solutions:
- leaking domain model in API responses and separating response model from domain model
- leaking data model in API responses and separating response model from data model
- leaking primary keys in non-aggregate root entities and abstracting data model with Entity Framework
- how everything having global identity affects local identities and what to do about it
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top