Yeah I had a good read of the concept. I do agree for most CRUD apps there will be no divergence.
My concern is that this breaks layering suggested by most architecture frameworks.
My concern is that this breaks layering suggested by most architecture frameworks.
But this kind of thing can work in a well-architected system too. You're basically just saying this API is pure CRUD. I simply record what the client tells me. Then you have to apply your business rules somewhere else. This is usually the event-driven approach. I just record commands/events, then some other code actions those, based on business rules.
Where I think this goes wrong is not realising the business rules have to go somewhere else. I see this with Django a lot. You get started with just pure CRUD then someone says "oh, we shouldn't allow that record because xyz", and the whole thing starts to become a mess.