3 ms·
Considering the databases often end up being the bottleneck. It may not always be wise. So its a small amount of data, but large computation it might be tempte
by UK-Al05 6y ago
Considering the databases often end up being the bottleneck. It may not always be wise.
So its a small amount of data, but large computation it might be tempted to do it on the application. But its a large amount of data, I/O maybe a problem in doing it on the app.
- TeMPOraL 6y agoThat's why I hedged my bets with "where appropriate" there :). You're of course right, and it could be that DB being a compute bottleneck is the most common case - but I've seen or been involved in projects where the bottleneck was DB I/O and processing unnecessary queries, because the application was doing most of the calculations.