eva
eva copied to clipboard
Workiva
A distributed database-system implementing an entity-attribute-value data-model that is time-aware, accumulative, and atomically consistent
Our caches should have sufficient metrics so we can identify churn (and set up alarms) on both our index node caches and index manager cache.
One of the main benefits of using Eva is for its point-in-time, and services often want to expose a transaction identifier of some kind to clients. Document best practices for...
We're a database that reifies time. You have to be specific about what time you're referring to! Include complete code examples of use and gotchas when you use the wrong...
What is syncDB? Why would you want to use it? When? Simple concrete examples.
A comprehensive look at log, tx-range, datoms, q, entity, pull, extant-entity? What are they, when and why would I want to use one over another, and how do they differ...
What happens when a transaction function fails. What happens when you throw an exception in a transaction function. How is this reported? How should you deal with it? Best practices....
What are rules in Eva? Recursive rules? How they work. Downsides, gotchas, and examples.
What is the problem? Why would I care? With good definitions in place, how do I check? Examples.
Summary of options for versioning your schema. What is it? Why would you want to do it? What are the different ways we can do it?