The VIVO architectural fly-in will be focused on bringing an architecturally-minded team together who individually represent distinct VIVO stakeholder constituencies for the purpose of developing architectural approaches required to address the direction of the project. The primary goal of the two-day face-to-face meeting will be to assess and document a plan for improving the VIVO application architecture towards enabling and realizing the technical efforts defined in the "Statement on VIVO's Product Direction for 2019".

The success of this effort relies on balancing the perspectives of:

...

University of Florida Research and Academic Center
Room 131
6550 Sanger Rd.
Orlando, FL 32827

Parking

Please park in the area marked as visitor parking (map)

Andrew will be renting a van for transport to/from hotel and meeting location
Image Added

Recommended hotel

...

LaQuinta Airport North

7160 N Frontage Rd, Orlando, FL 32812

Reasonable rates, AAA discount, newly rennovatedrenovated, very close to the hotel, upgraded wifi, breakfast included.

This is prime season to for Orlando (Dec-Mar) please book early to get a good rate.

Who

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

Agenda

...

2019-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

...