3 ms·

4/6 tests in there account for database requests. So yes, I would say that Tech empower is pretty important to gauge the performance and efficiency of web frame

4/6 tests in there account for database requests. So yes, I would say that Tech empower is pretty important to gauge the performance and efficiency of web frameworks. Personally, it helped me realize that my mistaken belief that nodejs was hella fast and that old Java based frameworks are slow. It also introduced me to Kotlin (I started on it to try Kooby) and overall love that I can at a glance see that for my chosen set of languages, which farmeworks-dbs are a good bet.

mattmanser 6y ago
The greatest trick that javascript ever pulled was to convince the latest generation of programmers that it was fast...
dathinab 6y ago
The problem is they account for _simple_ database requests. Which surely are common but long(er) running database requests or delegation to another service aren't super rare either. Similar some of the frameworks might have major reliability problems which can randomly "crop up" due to thread pinning and similar. I believe it should have some form of "chaos" test where instead of interacting with the DB it interacts with a another test server on both ends and the front and back connected server run through long random "chaos" simulation (and another version where a pre-recorded run is used for reproducibility).