28 October 2018

The Brief

What's the problem?

OrientDB (a hybrid database) has been problematic due to its poor documentation and support - it's time to change things up. What database should we move to?

What do we need to consider with the new database?

• Thoroughly documented
• Scale well (to up to 1 million elements?)
• Can easily query the data
• Actively supported (with stable releases)
• Create, Read, Update, Delete: nodes and edges
• Have a non-problematic license
• Martynas
  • Valuing edges as much as nodes
  • How could you add a permissions (read write access) layer? Library?
• Dharini
  • Able to release independent resources to third parties
  • Version control - draft & published (separate versions of tag elements?)
  • Different types of nodes & edges
  • Different forms of visualisation over the same data
  • In the future: can we build intelligence into the system for establishing relationships (like machine learning)
• Uta
  • Specify read and write access to each node and edge (permissions)
  • Search engine - fuzzy search

What are our options?

• Relational databases - MySQL, PostgreSQL, SQLite