One important step I've found helpful is asking if the candidate would like to receive feedback before sharing. This should also curb the risk of litigation.
The biggest problem with GraphQL in this regard is that it is a single endpoint. API gateways often define authorization rules, throttling rates, and caching times differently for each route. Consequently, you may need to write authorization, throttling, and caching logic in a separate layer or perhaps even in your microservices themselves.
Have you seen pictures of what drone props can do to skin? Even the handheld drones draw blood easily. The $500 phantoms can cause damage requiring stitches... Not sure a baseball is the best analogy.
In a cursory glance, this appears to be logic (token, redis, etc) that can be handled by Nginx+Lua. Is there any reason to do it this way vs the other?
Being an attendee from last year, I can guarantee you that it's people still filing in to find seats well into the presentation. The exit is towards the back left of where the camera is. People going to the right are looking for seats. It's still not an attractive angle.
I'm interested in seeing Google's Compute Engine show up in some of these benchmarks. Any reason why someone would not want to use them? Some benchmark's I've seen show them with awesome stats.