# Help on architecture

**URL:** <https://discuss.elastic.co/t/help-on-architecture/3971>\
**Category:** Elasticsearch\
**Created:** [February 24, 2011, 8:26am UTC](https://discuss.elastic.co/t/help-on-architecture/3971 "2011-02-24T08:26:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alheim](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@alheim](https://discuss.elastic.co/u/alheim)\
**Post date:** [February 24, 2011, 8:26am UTC](https://discuss.elastic.co/t/help-on-architecture/3971/1 "2011-02-24T08:26:18Z")

</div>

Hi everybody,

I'm currently evaluating elastic search to provide a super fast completion engine to our users.

The product is basically a social network enabling people to share content into groups.

When a user starts typing some words into the search bar, I would like elastic search to return results matching these words, for 4 types of objects : posts, users, tags, groups.

The query is not simple because a given user is allowed to see objects only if they share at least one group with him.

Example : if user A and user B are in group 1 and if user B publish in group 2, user A will not see the post.

What do you think ? Do I have to create 1 index per type of object ?

---

<div class="post-metadata">

**Author:** ![alheim](https://avatars.discourse-cdn.com/v4/letter/a/dec6dc/32.png) [@alheim](https://discuss.elastic.co/u/alheim)\
**Post date:** [February 24, 2011, 2:41pm UTC](https://discuss.elastic.co/t/help-on-architecture/3971/2 "2011-02-24T14:41:58Z")

</div>

Do I have to create one index per user ?

But what if I need to get all the content shared by users from my network ? Do I have to search into thousands of indexes ?

---

<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 6, 2017, 4:11am UTC](https://discuss.elastic.co/t/help-on-architecture/3971/3 "2017-07-06T04:11:32Z")

</div>

Closed on July 6, 2017, 4:11am UTC


