# Mongodb or other doc stores

**URL:** <https://community.siren.io/t/mongodb-or-other-doc-stores/618>\
**Category:** Siren Federate (Elasticsearch Plugin)\
**Created:** [February 4, 2023, 5:12pm UTC](https://community.siren.io/t/mongodb-or-other-doc-stores/618 "2023-02-04T17:12:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeffd](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jeffd](https://community.siren.io/u/jeffd)\
**Post date:** [February 4, 2023, 5:12pm UTC](https://community.siren.io/t/mongodb-or-other-doc-stores/618/1 "2023-02-04T17:12:54Z")

</div>

Good afternoon, has anyone investigated applying the siren federate technique to mongodb, aws es, or other similar es like document stores? Thanks, Jeff

---

<div class="post-metadata">

**Author:** ![renaud.delbru](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.siren.io/renaud.delbru/32/13_2.png) [@renaud.delbru](https://community.siren.io/u/renaud.delbru)\
**Post date:** [February 6, 2023, 8:50am UTC](https://community.siren.io/t/mongodb-or-other-doc-stores/618/2 "2023-02-06T08:50:20Z")

</div>

Do you mean porting the join capabilities of Federate to mongodb or other document stores?

---

<div class="post-metadata">

**Author:** ![jeffd](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jeffd](https://community.siren.io/u/jeffd)\
**Post date:** [February 6, 2023, 2:20pm UTC](https://community.siren.io/t/mongodb-or-other-doc-stores/618/3 "2023-02-06T14:20:23Z")

</div>

Hi Renaud, yes, either joins or siren federate plugin to replace or provide other options vs. elastic?

---

<div class="post-metadata">

**Author:** ![renaud.delbru](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.siren.io/renaud.delbru/32/13_2.png) [@renaud.delbru](https://community.siren.io/u/renaud.delbru)\
**Post date:** [February 7, 2023, 9:01am UTC](https://community.siren.io/t/mongodb-or-other-doc-stores/618/4 "2023-02-07T09:01:43Z")

</div>

Unfortunately, this is not an easy task, Federate architecture is closely based on Elasticsearch and Lucene architecture. Federate is using and extending Lucene and Elasticsearch at a low level, which is also the reason of the Federate performance. This is not a generic layer that can be ported to another system. A generic layer, which would be designed at a higher level, would not be able to offer the same performance.  
Therefore, building something similar for another document stores would mean developing a completely new software with most likely a different architecture.