Hi @FarisAhmed,
Please understand that Eventing itself uses DCP, but think of Eventing as more of a post-trigger environment to run a tiny lambda (where the server itself takes care of all the scaling and infrastructure so you don’t have to).
The only downsides to using a Java client DCP is that you have to ensure that your Java client is robust and reliable in the event of hard failures and failovers and it might take a little more coding on your part to interact in a performance fashion with the Data and Query services.
As @david.nault pointed out in a different post of yours (link) Kafka can also process data (it too uses DCP).
I guess it just comes down to the right tool for the right job, we really don’t have a preference.
Best
Jon Strabala
Principal Product Manager - Server