is there a limit on graphql response size

[1zg12]

I have an implementation leverage on dgs, which could server a response with varied data size.

At times, when the data size above 2GB, it would fail the process.

I didn't see any specs saying there is a hard limit of 2GB in dgs. However, I guess with current implementation it does seem like that's the limit.

Should this be included in the spec, or maybe the implementation should be updated ?

[srinivasankavitha]

That's interesting. We haven't run into this issue so far, perhaps we've not had such a huge response to handle. That said, we don't impose any specific limits in the framework. Sound like it is jackson that is having the problem when using the object mapper?

[1zg12]

I thought the same in the beginning as well, then jackson basically saying RestController shouldn't call writeValueAsString here.

dgs-framework/graphql-dgs-spring-webmvc/src/main/kotlin/com/netflix/graphql/dgs/mvc/DgsRestController.kt

Line 211 in 866f1d4

{ mapper.writeValueAsString(executionResult.toSpecification()) },

FasterXML/jackson-core#760

🤦

[srinivasankavitha]

OhI see. Thanks for providing the context. We can look into a fix. However, I'm not sure if we do want to handle larger than 2GB responses 🤔

[1zg12]

Personally, I think 2GB is no longer as large as it sounded like before. It's a 20 seconds transport time even for a 100MBps bandwidth.