5 ms·
> delaying performing the compute-intensive operation until an inconsistent sample crosses the reporting timescale Could this delay cause a wrong reporting? Si
by i_r7al 4y ago
> 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?
- uvdn7 4y agoNo 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).