# Elasticsearch vs Database

**URL:** <https://discuss.elastic.co/t/elasticsearch-vs-database/184653>\
**Category:** Elasticsearch\
**Created:** [June 6, 2019, 7:23pm UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653 "2019-06-06T19:23:46Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kdev/32/47676_2.png) [@kdev](https://discuss.elastic.co/u/kdev)\
**Post date:** [June 6, 2019, 7:23pm UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/1 "2019-06-06T19:23:46Z")

</div>

One of my customers is requiring me to save the data from the front-end to MySQL and to implement the searching features using ES.  
In this case, is there a need to store the data to MySQL?  
In my opinion, it's enough to use only ES stack for such the system.  
Am I wrong?  
Let me know please if someone has an opinion about this problem.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 6, 2019, 10:25pm UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/2 "2019-06-06T22:25:43Z")

</div>

Welcome! 🙂

What sort of data is it?

---

<div class="post-metadata">

**Author:** ![kdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kdev/32/47676_2.png) [@kdev](https://discuss.elastic.co/u/kdev)\
**Post date:** [June 7, 2019, 12:05am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/3 "2019-06-07T00:05:02Z")

</div>

Hi, @warkolm.  
Thanks for messaging me.  
The data types are like the kibana's visualization, panel, etc.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 7, 2019, 12:09am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/4 "2019-06-07T00:09:36Z")

</div>

It's not clear why you'd want to store those in a database, if you even could.

---

<div class="post-metadata">

**Author:** ![kdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kdev/32/47676_2.png) [@kdev](https://discuss.elastic.co/u/kdev)\
**Post date:** [June 7, 2019, 12:41am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/5 "2019-06-07T00:41:29Z")

</div>

Yeah, that's what I am thinking.  
I also think there is no reason to save the data to database.  
But client requires that the data is stored to database.  
So I wanted to know that is the right solution once again from the experts.  
So what you mean is that there is no reason that the data have to be saved to database, isn't it?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 7, 2019, 12:47am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/6 "2019-06-07T00:47:35Z")

</div>

Kibana visualisations/dashboards ettc are not designed to be stored in a database. You could, but it's be a json blob as opposed to a properly formatted row.

---

<div class="post-metadata">

**Author:** ![kdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kdev/32/47676_2.png) [@kdev](https://discuss.elastic.co/u/kdev)\
**Post date:** [June 7, 2019, 1:46am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/7 "2019-06-07T01:46:16Z")

</div>

Got it, @warkolm.  
Thanks for your help.  
I have another question.  
My situation now is ES was installed on ubuntu server and I need to restore a cluster from my local machine.  
In this case, how should I set the path.repo in the server's elasticsearch.yml?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 7, 2019, 1:50am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/8 "2019-06-07T01:50:44Z")

</div>

It's better if you create a new topic for that question, it'll make it easier for everyone to help you 🙂

---

<div class="post-metadata">

**Author:** ![kdev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kdev/32/47676_2.png) [@kdev](https://discuss.elastic.co/u/kdev)\
**Post date:** [June 7, 2019, 1:51am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/9 "2019-06-07T01:51:15Z")

</div>

Got it.  
Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2019, 1:51am UTC](https://discuss.elastic.co/t/elasticsearch-vs-database/184653/10 "2019-07-05T01:51:19Z")

</div>

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