Looking to step into the world of Domain Driven Design with a simple project for my personal use. The project is a simple calculator to evaluate different retirement scenarios between the old DOD "High-3" retirement and the new "BRS" retirement.
The issue I'm having as I go through this (very simple) project is that I cannot identify any object that really has a unique identity. The Ubiquitous Language consists of: Retirement, Employee, TSP, High3, BRS, Contribution, etc. But none of these really have any GUID.
In most applications, an employee probably does differ from another employee or a retirement does differ from someone else's retirement. But for this project, a retirement with one set of attributes should be considered the same as another retirement object with the same set of attributes.
Or maybe I should view that the set itself (of attributes) is considered unique and, therefore, there can only be 1 set of attributes for a retirement.
Am I thinking about this incorrectly or is this not a good project for DDD? Again, I wanted to expand my design and architecture knowledge with a homemade project.