# Scaling with regard to Nested vs Parent/Child updates

**URL:** <https://discuss.elastic.co/t/scaling-with-regard-to-nested-vs-parent-child-updates/10777>\
**Category:** Elasticsearch\
**Created:** [February 18, 2013, 2:50pm UTC](https://discuss.elastic.co/t/scaling-with-regard-to-nested-vs-parent-child-updates/10777 "2013-02-18T14:50:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dereko](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@dereko](https://discuss.elastic.co/u/dereko)\
**Post date:** [February 18, 2013, 2:50pm UTC](https://discuss.elastic.co/t/scaling-with-regard-to-nested-vs-parent-child-updates/10777/1 "2013-02-18T14:50:19Z")

</div>

I'm running a proof of concept for us to run nested queries on more "normalised" data in ES.

e.g. with nested

Customer -\>  
- name  
- email  
- events -\>  
- created  
- type

Now I have a situation where a list of events for a given customer can be moved to another customer. e.g. Customer A has 50 events  
Customer B has 5000 events

I now want to move all events from customer A into Customer B

At scale with millions of customers and queries are run on this for graphs in a UI is Parent/Child more suitable or should nested be able to handle it?

What are the pros and cons in my situation?

---

<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, 2:50am UTC](https://discuss.elastic.co/t/scaling-with-regard-to-nested-vs-parent-child-updates/10777/2 "2017-07-06T02:50:57Z")

</div>

Closed on July 6, 2017, 2:50am UTC