A new test type that involves outgoing REST communication

[martintmk]

In modern applications, especially in microservice architectures, outgoing REST calls play a critical role in communication with external APIs and services. While the current test suite covers many scenarios, there isn’t a dedicated test type that evaluates the performance of HTTP clients during these REST interactions.

The idea is to create a test that simulates a typical REST communication flow, which would involve:

• Constructing and sending an HTTP request.
• Serializing the request payload.
• Receiving the response.
• Deserializing the response.

This test would effectively assess the performance and robustness of various HTTP clients across different frameworks and languages. By using a minimal REST dependency as the data source (instead of a database, as in some of our current tests), it can directly measure client-side REST handling capabilities.

The specification for the new test type is TBD (it could be just a variation of existing single database query). I am just wondering if you would entertain such idea before investing more time into it.

[joanhey]

I think that is the same that the single database query.
The json encode-decode are similar in performance, in all frameworks.

PD: some fws have worst performance decoding application/x-www-form-urlencoded and multipart/form-data.