Table architecture for relevancy scores
Hello,
I have a postVotes table linking users to posts. Currently using table aggregates to efficiently count total votes per post for display.
Now I need to implement post relevancy scoring (combining vote count + time decay), but this requires accessing vote data that's abstracted behind the aggregate layer, so I can't compute relevancy without n+1 querying each time, or going through big full table cron computes.
Is there a recommended approach to expose vote counts for scoring calculations while maintaining the aggregate's performance benefits for display?
This is more of a table architecture question. Thanks !
I have a postVotes table linking users to posts. Currently using table aggregates to efficiently count total votes per post for display.
Now I need to implement post relevancy scoring (combining vote count + time decay), but this requires accessing vote data that's abstracted behind the aggregate layer, so I can't compute relevancy without n+1 querying each time, or going through big full table cron computes.
Is there a recommended approach to expose vote counts for scoring calculations while maintaining the aggregate's performance benefits for display?
This is more of a table architecture question. Thanks !
