News for hackers. Stuff that matters.
Re:Cache made consistent: Meta’s cache invalidation solution by i_r7al on Wednesday June 08, 2022 @10:05PM (#31676841)
> delaying performing the compute-intensive operation until an inconsistent sample crosses the reporting timescale

Could this delay cause a wrong reporting? Since the source of truth (the DB) could already received multiple mutate events of the data Polaris trying to verify? How do you handle this case?

Re:Cache made consistent: Meta’s cache invalidation solution by uvdn7 on Wednesday June 08, 2022 @10:16PM (#31676905)
No actually. When a sample has crossed the reporting timescale, and it's inconsistent. Regardless of if the db changes later or cache becomes consistent later, at the moment it's still an anomaly (inconsistency in this case).