graphql-go-tools

https://github.com/wundergraph/graphql-go-tools/blob/dcd50bd... Each iteration of this benchmark measures the aggregate performance of - 1x ParseObject - 3x AppendObject - 3x MergeNodesWithPath - 1x PrintNode - 1x bytes.Equal comparison of two byte slices So the benchmark isn't really measuring MergeNodesWithPath, it's measuring a much larger composite operation, which includes (multiple) calls to MergeNodesWithPath but also all of the above listed calls as well. If you want to measure MergeNodesWithPath, you would need to have each iteration of the loop do a single MergeNodesWithPath call, on the same JSON method receiver, and with the same input parameters. edit: similar issues exist in many/most of the other benchmark functions as well

I've taken a very similar approach and built a GraphQL tokenizer and parser (amongst many other things) that's also zero memory allocations and quite fast. In case you'd like to check out the code: https://github.com/wundergraph/graphql-go-tools

Some people mis-read this post as "showing" love to a company in the application. This is not what I meant, so I'd like to clarify this with a story. Prior to starting WunderGraph, I've worked for a Full Lifecycle API Management company. It's was my best paying and most satisfying job before cutting my salary almost half to make my startup burn as little as possible. I found this company because they had an open source codebase, written in Go. Coincidentally, I've built a library (https://github.com/wundergraph/graphql-go-tools) to build GraphQL API gateways, also written in go. At that time, they were only supporting REST. So I wrote them and offered the opportunity to add GraphQL to their API management capabilities. That was it, perfect match. Fast forward 2.5 years later and they have all sorts of powerful GraphQL API management capab

Congrats on getting this open sourced! Wundergraph takes a really interesting approach to solving stitching APIs together, taking care of a lot of production concerns around security, performance, and caching that can come into play with GraphQL. This also uses the awesome graphql-go-tools (https://github.com/wundergraph/graphql-go-tools) under the hood which is way more performant than other JavaScript GraphQL implementations.