Just read my first book on DDD ("Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F#" by Scott Wlaschin in case it makes any difference), and came away with the distinct impression that DDD is great for batch processing, but not necessarily so good for other things.
His example was an order processing system, where the input is a paper form from the customer. The unvalidated data goes into the first stage in the workflow, where it's converted to a validated order (or bounced back if invalid), which is the input to the second stage and so on. The end result is a bunch of events indicating what happened and/or should happen next. This is very much an uninterrupted pipeline.
By contrast, the majority of my work involves pulling data from a database, displaying it on a web page of desktop window, waiting for the user to make some modifications, and then saving the modified data back to the database. I can't really see how DDD would help there. It's only really a one-stage workflow.
Did I miss something, or is DDD only really useful for batch processing?