# Relational data

**URL:** <https://discuss.elastic.co/t/relational-data/259082>\
**Category:** Elasticsearch\
**Created:** [December 18, 2020, 10:59am UTC](https://discuss.elastic.co/t/relational-data/259082 "2020-12-18T10:59:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jean-Marc\_Autexier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jean-marc_autexier/32/51342_2.png) [@Jean-Marc\_Autexier](https://discuss.elastic.co/u/Jean-Marc_Autexier)\
**Post date:** [December 18, 2020, 10:59am UTC](https://discuss.elastic.co/t/relational-data/259082/1 "2020-12-18T10:59:07Z")

</div>

Hi,

I think we all know the limits of elastic when having relational data....  
There are things you can solve (using de-normalization, nested, parent-child, lookups) but sometimes your uses cases require query time joins (n:m relations, complex queries...).

So simple question: what is your preferred storage to solve this for large data? a relational database (which one?), a graph database?, ...

br,  
Jean-Marc

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 18, 2020, 11:14am UTC](https://discuss.elastic.co/t/relational-data/259082/2 "2020-12-18T11:14:18Z")

</div>

I would say that depends entirely on the requirements. It is impossible to give a generic answer as there is no system that does not involve some kind of trade-off.

---

<div class="post-metadata">

**Author:** ![Jean-Marc\_Autexier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jean-marc_autexier/32/51342_2.png) [@Jean-Marc\_Autexier](https://discuss.elastic.co/u/Jean-Marc_Autexier)\
**Post date:** [December 18, 2020, 12:21pm UTC](https://discuss.elastic.co/t/relational-data/259082/3 "2020-12-18T12:21:18Z")

</div>

I fully agree with what you say.

What I expected as response is something like "we are using XYZ because we had those requirements, and we made good/bad experience with it".

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 18, 2020, 12:34pm UTC](https://discuss.elastic.co/t/relational-data/259082/4 "2020-12-18T12:34:44Z")

</div>

In my experience generic questions do not get responded to as frequently as more targeted ones. If you have a use case you would probably get more responses if you described it and it’s characteristics and asked for advice. This may s as Lao better be asked in a different forum that is not do Elasticsearch focused.

---

<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:** [January 15, 2021, 12:34pm UTC](https://discuss.elastic.co/t/relational-data/259082/5 "2021-01-15T12:34:52Z")

</div>

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