...

• Justin Littman
  
• Ralph O'Flinn
  
• Alex Viggio
  
• Benjamin Gross
  
• Brian Lowe
  
• Huda Khan
  
• Jim Blake
  
• Richard Outten
  
• Andrew Woods 

Agenda

To be developed2019-01-29 to 30 - VIVO Arch Fly-in f2f Meeting

Requirements

1. VIVO must support ingest rates of x-number of triples per hour

2. VIVO must support total scale of y-number of triples
3. VIVO must support the removal of triples, regardless of the number of triples or size of graph
4. VIVO must support response times of < 2sec for profiles, regardless of number of relationships
5. VIVO must service any frontend user interface via an API
6. VIVO must support API-driven integration tests
7. VIVO must support the swappability of the following components
   1. Search index
   2. Triplestore
   3. Asset store
8. VIVO must support ingest without stopping other components (indexer)
9. VIVO must support configuration update without requiring application restart

Considerations

1. VIVO should be designed towards being "cloud-ready"

Thoughts / Notes / Resources

...