Re:Building a recommendation engine inside Postgres with Pyt...
by systemvoltage on Tuesday October 26, 2021 @06:17PM
(#29007067)
That's the job of an API IMO.
[ Parent
| on HN ]
Re:Building a recommendation engine inside Postgres with Pyt...
by uoaei on Tuesday October 26, 2021 @07:19PM
(#29007651)
An API makes sense for this case when you won't be throwing away a lot of the raw data in favor of the processed/transformed data.
But doing a lot of these operations on-server makes sense when there's a significant volume of highly parallelizable transformations which need to be done on the data before it's usable.
Of course the best solution is likely to be a happy medium between the two, where simple low-level transformations are done on-server and the rest of the data preparation is done as the data is transferred to the client.
Re:Building a recommendation engine inside Postgres with Pyt...
by mrbungie on Tuesday October 26, 2021 @07:55PM
(#29007977)
Not in data processing. There are cases where you have so much data that is better to bring computation to data rather than the other way around.
Re:Building a recommendation engine inside Postgres with Pyt...
by FridgeSeal on Tuesday October 26, 2021 @09:52PM
(#29008730)
Having dealt with the fallout of a database that’s had hundreds of stored procedures and custom code stapled into it: never again.
It was so hard to debug, so hard to safely maintain these procs, and a general nightmare