How can you know if something is "pure CRUD solution" ("just CRUD")? It seems complexity is a hard thing to define for the various DDD proponents. Everyone says if it's "just CRUD" you don't need DDD. What does "just CRUD" mean? Every application I've made has CRUD operations somewhere.
I realize there are different types of patterns within DDD and much is a mindset (common vocabulary), as you have to know the domain regardless, but if a company is going to invest in a Business Analyst and the whole nine-yards, I'd like to know when that is overkill. "Just CRUD" is pretty vague.
I have seen this, Is Domain Driven Design useful / productive for not so complex domains?
In there "If there's not much behavior, which is to say, you're mostly storing data, and not acting on that data, there may be much less value in building out that domain layer." This is "just CRUD," but I've never seen a system that didn't "acting on that data" either.
For example, Let's say someone is building a Hospital Application, lots of stuff there, essentially a small city. That's complex, but I don't know why other than the sheer amount of things that have to be accounted for, but end the end it is CRUD.
Intuitively, I know a hospital application complex, but I do not know why it is complex in the sense that DDD mean complexity.
What is a non-complex example?
Edit: Sorry, I forgot to say that I know what CRUD means.