What kinda of performance (response times) and scalability (concurrent requests per second) are y'all seeing?
With standard GET requests against a sql database, returning 20 records at a time let's say.
I'm having issues at less than 10 concurrent requests.
kevinsproles
>All comments
@kevinsproles Hello. It should be mentioned, that this is not the "problem" of nestjsx/crud itself, but the one for typeorm, because nestjsx/crud is just a boilerplate code for your controllers and services and under the hood they use typeorm.
Asking the question about performance and scalability: using the ORM will always produce a new layer of abstraction to the database connection, which, of course, will somewhat slow down the request processing. If you prioritize performance more than comfortability, you should use the original driver of your database, but then you will not have this comfortable CRUD generator and other tools, that simplify your developer life.
Hope I explained it all clear! :)
sinnrrr
on 13 Dec 2020
Related issues
josimarz
路
4Comments
cjancsar
路
4Comments
dulkith
路
3Comments
mkelandis
路
4Comments
basvdijk
路
5Comments
Most helpful comment
@kevinsproles Hello. It should be mentioned, that this is not the "problem" of
nestjsx/cruditself, but the one fortypeorm, becausenestjsx/crudis just a boilerplate code for your controllers and services and under the hood they usetypeorm.Asking the question about performance and scalability: using the ORM will always produce a new layer of abstraction to the database connection, which, of course, will somewhat slow down the request processing. If you prioritize performance more than comfortability, you should use the original driver of your database, but then you will not have this comfortable CRUD generator and other tools, that simplify your developer life.
Hope I explained it all clear! :)