Tracking searched JSON documents

We are evaluating based on our requirements and not sure how to handle these.

We have decided to sink our events as JSON using Kafka Elasticsearch Sink Connector. The source is the DB. Now our primary document store is Elastic.

  1. How do we keep track of what is searched ? Our searches return notification messages and the user does not need to view what he has already viewed. Since the source for searches is Elastic it is tricky to keep track of what is already read ourselves. Maybe if I model the JSON with a UUID v4 then I can store something in Elastic if it is searched already.

  2. This brings up another question. What is the need for a Spring Data Elastic Micro Service in front of Elastic. What are the usecases the forum is aware of ? I can have custom business logic there. I understand.


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.