Ideas · Builder Notes
Keeping gateway latency flat as history grows
Kognita alpha bounded its gateway decision reads to rows in force, after closed history made overhead grow with every policy change.
Before
Gateway overhead grew with closed history. Every decision loaded every policy, revocation, drill, use case and model card, then discarded the closed rows in Python.
After
Decision reads are now bounded in the query to rows in force at the decision time.
Gateway overhead stopped depending on how much history a store had.
Why it matters
The evidence length was not the cost. Measuring before guessing pointed at the right fix.
Effective-dated history is the right model for audit, but it needs indexes and bounded reads to stay fast.
Audit-friendly data models need performance tests with years of history in the store.
Sources
Kognita is an open-source alpha. This note comes from Kognita PR #45 in the Kognita repository.