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
How schema relationships can be visualized as a graph. How branches affect queries. How to design schema and/or queries to deal with this. "Traversing up a tree" in a query....
- Brief discussion of the built-in attributes and their contracts, especially the core meta-attributes. - Present a variety of ways to paint yourself into a corner. - How to design...
Cross-database queries: what, why, why not, how, examples.
Simple examples of enforcing custom schema constraints through transaction functions. Possible example - "how to write an atomic increment."
What does it even mean to embed a data structure in Eva? Why would I want to do that? How should I go about doing it? What are common pitfalls,...
What is a cycle in your relationship graph? Why might you care? If you do, how could you detect cycles with Datalog?
Sometimes I want a query to return a value – but optionally, conditionally, or only if this attribute exists on the entity. How do I do these things?
What are the implications of querying within a transaction function? Why would I do this? Why would I *not* do this? Specific examples of right and wrong ways.
- Brief discussion of storage implementation details, storage backend constraints, etc - Ballpark napkin-worthy size limitations on values, quantity limitations on queries, etc. - Write up several examples of how...
Eva is a strongly consistent system where there exists a small period of communication synchronization. We should create an artifact documenting and elaborating on this behaviour.