When starting your domain model as per suggested docs: https://www.esdm.io/getting-started/your-first-model-with-ai/ it will organize the files as per linguistic hierarchy.
Likewise frameworks scaffold projects as per technical citizens: controllers, routes, models, views... you name it. For frameworks, this is good for a hobby/weekend project, but your project seen outgrows.
That was an intro to one of my talks (first 2.5 minutes): https://www.youtube.com/watch?v=GkPXdC32t3Q
Now, the resulting domain model is much closer to the business we are operating in (in comparison to the pure technical citizens of frameworks), points given ;)
But overall we organize our thoughts more around the business capabilites or processes which often is reflected in strategic or tactical architecture design.
A naive way would be saying I call for a formal language to describe any sort of architecture at first, which brings the structure - no that would be naive (But hey "subdomain" is already present 😁).
But a way to connect esdm to one such. However that looks like. I can say, I struggle(d) a lot with that. I now have something - but it still feels very fragile.
For reference:
When starting your domain model as per suggested docs: https://www.esdm.io/getting-started/your-first-model-with-ai/ it will organize the files as per linguistic hierarchy.
Likewise frameworks scaffold projects as per technical citizens: controllers, routes, models, views... you name it. For frameworks, this is good for a hobby/weekend project, but your project seen outgrows.
That was an intro to one of my talks (first 2.5 minutes): https://www.youtube.com/watch?v=GkPXdC32t3Q
Now, the resulting domain model is much closer to the business we are operating in (in comparison to the pure technical citizens of frameworks), points given ;)
But overall we organize our thoughts more around the business capabilites or processes which often is reflected in strategic or tactical architecture design.
A naive way would be saying I call for a formal language to describe any sort of architecture at first, which brings the structure - no that would be naive (But hey "subdomain" is already present 😁).
But a way to connect esdm to one such. However that looks like. I can say, I struggle(d) a lot with that. I now have something - but it still feels very fragile.
For reference: