Much like most things engineers bitch about, the tool isn't to blame here (as you say yourself) - it's the wrong tool for the wrong job.
There's nothing about DDD that says you can't make a simple CRUD API, if that's all that is required.
DDD's principle value is one of ubiquity (sold as "Ubiquitous Language" but I posit that "Ubiquity" is more accurate) - does your code do what the organisation does, and vice versa?
Not just using the same terminology, but using the same workflow.
Now if what the organisation does is basic stuff, then your code should be basic, too.
If there is an asymmetry between what the org and code do.. there's pain.
There's nothing about DDD that says you can't make a simple CRUD API, if that's all that is required.
DDD's principle value is one of ubiquity (sold as "Ubiquitous Language" but I posit that "Ubiquity" is more accurate) - does your code do what the organisation does, and vice versa?
Not just using the same terminology, but using the same workflow.
Now if what the organisation does is basic stuff, then your code should be basic, too.
If there is an asymmetry between what the org and code do.. there's pain.