---
# System prepended metadata

title: Graphql Nested Query Problem

---

Graphql Nested Query Problem
===



|                             | One resolver                                                                | Multi-resolver                                                                                                 |
| --------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Num of involking Lambda** | 1                                                                           | >1 (depends on num of child nodes)                                                                             |
| **Execution Duration**      | maybe faster                                                                | maybe slower                                                                                                   |
| **N+1 Problem**             | No (We can use the selected fields to decide whether there's table joining) | Yes (because need 1 more sql query to get child nodes data)                                                    |
| **Child nodes filtering**   | No                                                                          | Yes (because another lambda will handle a certain child node, so it will know where there're filtering fields) |
