The use case of having keywords in a table/database is also valid in my environment.
If the use cases require you to block data from leaving the endpoints when detecting the keywords EDM isn't a valid solution (yet). EDM can only detect data when it has already left the endpoint and thus fails on the use cases. I've worked/evaluated both McAfee and Microsoft's solutions for DLP and they both allow the implementation of dictionaries with keywords which you can link to from your policies.
I don't know if Aadi has this same endpoint-like situation, but I do and I am currently having copies of keywords lists that I have to update well over 100 times if only 1 item in the keyword lists has to be changed.... Also every applicable copy of the same list of dictionaries is send over and loaded by the endpoint agent creating unnecessary overhead.
With the implementation of dictionaries my use cases and administration would just have been so much easier.