You do realize that every time #spring #graphql calls an endpoint when stitching, it does so through a REDIRECT which drops a threads, goes outside the DMZ, comes back in and reissues the request/response/thread and calls the new endpoint. This happens for EACH ENDPOINT it has to stitch together; perfect for MITM attacks and high I/O overhead and hogging processing (until all those threads get cleaned up by GC).

Don't believe me? See diff between Forward and Redirect ( http://www.differencebetween.net/technology/difference-between-forward-and-redirect/ )