# Is this approach feasible for my usecase?

**URL:** <https://discuss.elastic.co/t/is-this-approach-feasible-for-my-usecase/28110>\
**Category:** Elasticsearch\
**Created:** [August 26, 2015, 2:01pm UTC](https://discuss.elastic.co/t/is-this-approach-feasible-for-my-usecase/28110 "2015-08-26T14:01:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![N\_M\_10](https://avatars.discourse-cdn.com/v4/letter/n/f19dbf/32.png) [@N\_M\_10](https://discuss.elastic.co/u/N_M_10)\
**Post date:** [August 26, 2015, 2:01pm UTC](https://discuss.elastic.co/t/is-this-approach-feasible-for-my-usecase/28110/1 "2015-08-26T14:01:00Z")

</div>

We have 3 node ES cluster and there is a AWS LB in front of this cluster, after retrieving search results, our user clicks on one of them and we want to send this selected item back to ES to update some counter/boost value.

Should we use

Client -\> retreive result from -\> ES -\> send selected item to -\> Logstash -\> AWS LB -\> increament counter/\_boost for selected value in ES ?

Or there is much better option available in terms of scalability ?

---

<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, 2017, 11:53pm UTC](https://discuss.elastic.co/t/is-this-approach-feasible-for-my-usecase/28110/2 "2017-07-05T23:53:45Z")

</div>