...
- 2018-01-10-vivo-fly-in-planning.mp3
Questions / Observations for Straw-chitectures
vivo_arch_v1.png
- VIVO is separate from read-only sites
- Triplestore is central to VIVO
- Difference between Source Systems and staging/loaders?
- External Solr gets loaded by a loader?
vivo_arch_v3.png
- Scalable ingest
- No focus on refactoring VIVO
- How are loaders triggered?
- How are updates managed, from the UI?
VIVO Product Evolution Straw
- Similar to above
- No focus on refactoring VIVO
Screen Shot 2018-12-20
- Focus on VIVO refactoring
- How is performance and scale addressed?
- Is the frontend decoupled from the APIs?
- Server-side or client-side frontends?
Future VIVO Example
- Focus on VIVO refactoring
- Maybe config does not need to be in a triplestore
VIVO 2.0 Arch
- Focus on VIVO refactoring
- Similar to above
arhitectura-vivo
- Addresses updates from UI and other sources
- Can service layer become the core VIVO app w/ content sources externalized?
VIVO arch brainstorming-2
- No focus on refactoring VIVO
- Similar to Duke?
- Loader model
- What is the interation between webapps and content stores? API?
- What does deployment look like?
- Where does the VIVO ontology come into the picture?
ACTIONS
Collection of existing architecture diagrams / resources
...