I love that I don't need to loop against master records due to data parallelism. We haven't used data services yet, but are excited to use when we have the need for our own APIs.
The product isn't always easy to use because of the items listed in the cons section.
I'd really like to see:
1. The ability to embed dictionary values in SQL components the way you can with parameters
2. Be able to use jobflow components on a CloverDX as well as a server project. A big part of my clover work is the design of moving between jobflows and graphs. I have found developing with a CloverDX project useless because I can only design/code jobflows on a server project.
Data services can be used to create web services
Jobflow components can only be used on server projects
Dictionary values cannot be embedded in SQL statements
Managing meta data within jobflow/graphs can be tedious (as compared to SSIS)
Not much documentation other than Clover documentation (when I Google CloverDX topics)
It is very useful for me because I need to process huge data daily. Its wonderful speed I allows to improve processing time of the data.