# Use case for App Search?

**URL:** <https://discuss.elastic.co/t/use-case-for-app-search/255436>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [November 15, 2020, 12:18pm UTC](https://discuss.elastic.co/t/use-case-for-app-search/255436 "2020-11-15T12:18:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nickchow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickchow/32/42547_2.png) [@nickchow](https://discuss.elastic.co/u/nickchow)\
**Post date:** [November 25, 2020, 6:00pm UTC](https://discuss.elastic.co/t/use-case-for-app-search/255436/2 "2020-11-25T18:00:16Z")

</div>

Hi ismarslomic,

Interesting use case!

First, to directly answer your questions:

1. Nested objects: that's correct, you'd likely need to reconsider how you structure your data using suggestions from [that thread](https://discuss.elastic.co/t/nested-field-in-app-search/252233/2).
2. There isn't a Java-based client for App Search right now. Working directly with our APIs is quite pleasant though – we have put a lot of thought into making our APIs easy to use!
3. There is most certainly [active work on App Search](https://discuss.elastic.co/t/is-there-any-active-development-or-just-bug-fixes/255431/4) – every release brings exciting new features! And App Search is used to power [mission-critical search](https://www.elastic.co/customers/happyfresh) by [many companies](https://www.elastic.co/elasticon/archive/2020/global/customer-success-at-honeywell-with-elastic-enterprise-search).

On another note – searching over documents that are 2MB in size may have some performance implications. Would it be possible to break those into smaller individual documents? (Perhaps that may change how you architect the fields as well).

Hope that helps,  
Nick

---

_[View the full topic](https://discuss.elastic.co/t/use-case-for-app-search/255436)._