> Some have already optimised the heck out of their data retrieval and writes
Then they have likely not very much to gain from framework speedup either.
The fact that raygun could introduce a "asynchronously hand off to our queuing service" says quite clearly that "already optimised data retrieval and writes" is not the case that we are talking about.
Asynchronously dropping something on to a queue, possibly leaves the queue client implementation as the suspect slowing node down.
But assuming that dropping something on to a queue is incredibly fast. Switching how you serve your http requests can increase performance by some multiples because it would be the largest constant in time taken assuming a very fast queue drop.
Although I agree, if your at that point your probably serving all your requests fine anyway.
Then they have likely not very much to gain from framework speedup either.
The fact that raygun could introduce a "asynchronously hand off to our queuing service" says quite clearly that "already optimised data retrieval and writes" is not the case that we are talking about.