For making the handler functions run in parallel, do I need to do anything else other than making the backing function return a Mono object? I've done that but I don't know how to check whether they are indeed running in parallel. The @trace directive isn't returning anything and the response time is also the same (sometimes even more).
I've built the trace directive myself, not sure if it is working with newest Spring for GraphQL versions. I think the easiest is to use the TracingInstrumentation (www.graphql-java.com/documentation/instrumentation/#apollo-tracing-instrumentation) provided by graphql-java. You can create and instance yourself and return it from a Spring configuration @Bean method. Mono should work out of the box, maybe you need to configure the thread pool.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
Great video! Hadn't been able to find any good documentation on doing this well with Spring for GraphQL
Great video! Very clear and concise
wow. this is amazing. thanks
For making the handler functions run in parallel, do I need to do anything else other than making the backing function return a Mono object? I've done that but I don't know how to check whether they are indeed running in parallel. The @trace directive isn't returning anything and the response time is also the same (sometimes even more).
I've built the trace directive myself, not sure if it is working with newest Spring for GraphQL versions. I think the easiest is to use the TracingInstrumentation (www.graphql-java.com/documentation/instrumentation/#apollo-tracing-instrumentation) provided by graphql-java. You can create and instance yourself and return it from a Spring configuration @Bean method.
Mono should work out of the box, maybe you need to configure the thread pool.