More Details about the Application Architecture

[jeffreywstevens]

I am working on implementing Elasticsearch to empower more innovative use of data in my ecosystem which is mostly SQL-based. We have many use cases but high-performance fuzzy and phonetic matching is one that would provide great lift especially for consumer client applications. Research into a better understanding of Elastic, with best practices for fuzzy and phonetic matching, led me to Zentity.io. My hope is that can streamline and encapsulate the details into one package potentially saving me expensive development work.

However, my knowledge of Elasticseach is increasing but still early. Do you have any more details of the application architecture of Zentity.io? I want to know what features of Elastic it uses or builds upon and what have you built that is proprietary. Is an "entity resolution job" something you built or does it utilized something in Elasticsearch. I know Elastic has some pipelining features but again I am just getting started. Thank You in advance!