From 47115bee3da89d0fc7352982dfadb440ab28ca8a Mon Sep 17 00:00:00 2001 From: Tanmay Deshpande Date: Sun, 20 May 2018 18:22:04 +0530 Subject: [PATCH] First ADR Doc --- .../0001-use-elasticsearch-for-search-api.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/adr/0001-use-elasticsearch-for-search-api.md diff --git a/doc/adr/0001-use-elasticsearch-for-search-api.md b/doc/adr/0001-use-elasticsearch-for-search-api.md new file mode 100644 index 0000000..788454e --- /dev/null +++ b/doc/adr/0001-use-elasticsearch-for-search-api.md @@ -0,0 +1,27 @@ +# 1. Use Elastic Search for exposing enterprise wide search API. + +Date: 2018-05-20 + +## Status + +Accepted + +## Context + +There is a need of having an API exposed which can be used to search enterprise wide common data model. + +The data currently resides in a RDBMS database, it is difficult to expose micro-services directly querying out of RDBMS databases since the application runs out the same environment. + +There are options like ElasticSearch or Solr where data can be replicated. + +## Decision + +Use ElasticSearch for data indexing + +## Consequences + +Data needs to be replicated across the ElasticSearch cluster. This separate cluster needs proper maintenance. + + * Near-real time data replication is required. + * Additional cost of maintaining the ElasticSearch environments +