Ask questions and see you at February, 7th, 8.PM. CET: youtube.com/c/bienadam
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions.
Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
Hi Adam,
I'm looking for integrating elastic search in a wildfly with mysql project for improving searching.
First of all , is it better to split my data between mysql and elasticsearch or have elasticsearch as a cache ,which means data duplication?
I have two options for the integration: internally or externally:
a) externally by using A CDC approach like debezium seems good enough but it has an extra complexity ,maintenance mostly, for project administators and i will like to avoid it. Also this approach works only for cache (not if i want to split data between different datastores) , but it provides a good consistency model for me to ensure that if sth commits to mysql will go next to elasticsearch, also if sth goes wrong to ES , i can restore ES storage to a previous ex. one week ES backup and replay the command history and recreate the correct state to ES.. Am I correct on this?
b)In internal integration case: What is the best approach to handle persisting data in elastic search in a specific jee transaction which on sucesfull commit persist data on mysql ? I thought sth like firing CDI event on sucesfull transaction commit which will persist data to ES also and with some scheduled timer checkup periodically if everything is ok between ES and Mysql state. But this also only suitable for cache, not for data split. I would like your opinion for both cache and data split case.
Thanks in advance,
Vaggelis
big fan of the show...