web-frameworks
web-frameworks copied to clipboard
Create new types of tests
Hello,
Currently, the web-framework benchmark tests an empty endpoint.
However, web frameworks are about more than just request delay; they are mainly about processing complex tasks like JSON serialization, object composition, DB requests, etc.
Have you ever considered enriching the benchmark with new types of tests? It could provide a more comprehensive evaluation of web frameworks.
Imagine the following endpoints:
/ - the current behavior, we check the response time
/external-service - we call external services (a function that does a sleep)
/serialization - we send and receive a large JSON body in POST request with few query parameters
/http-client - we test the standard HTTP client and load a large file hosted in the server itself
/web - we do complete web scenarios with JSON in requests, DB requests, data transformations, and large JSON in response
We also deprecated the endpoints : /user/{id} /user Because they do not bring value compared to the / endpoint
The current benchmark does not need to be updated. But each new piece of code that is not a framework update must implement that logic.