Software engineer with over 10 years experience in different technology stacks, architecting, developing, CI/CD and leading teams. Currently working with Java, Node.JS and Serverless
That also make sense, but usually when I do a DDD I start with domain and create hexagonal architecture (ports and adapters) and with this approach I came to conclusion that I just care about a list of domain objects and don't care yet how they will be provided (by CSV or JSON or other means) which still leads to your answer that CSV parsing remains in application service.
Interesting... I usually start from the application layer and that helps me to decide what should be part of the domain. For me is easier start with the things that are more concrete ... but well, each person solves the problems in different ways =)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my opinion you should start by writting the application service and do the parsing there...
That also make sense, but usually when I do a DDD I start with domain and create hexagonal architecture (ports and adapters) and with this approach I came to conclusion that I just care about a list of domain objects and don't care yet how they will be provided (by CSV or JSON or other means) which still leads to your answer that CSV parsing remains in application service.
Interesting... I usually start from the application layer and that helps me to decide what should be part of the domain. For me is easier start with the things that are more concrete ... but well, each person solves the problems in different ways =)