Giters

Workiva / eva

A distributed database-system implementing an entity-attribute-value data-model that is time-aware, accumulative, and atomically consistent

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Degenerate System State Exploration

tylerwilding-wk opened this issue · comments

commented

The idea here is that we should have at least some explicit exploration and categorization of system behavior under duress from edge case scenarios. Examples:

  1. What is the behavior of the transactor / transaction log, indexer / indexes with datoms that fall far outside of the contract we've designed for? (Eg, What happens when we put a few thousand 1MB datoms into the indexes? Can we come up with cases that can consistently crash our index processes?)
  2. What is the behavior of the system for very thrashy datoms?