Persistence

[geomat0101]

Some options:

• Traditional RDBMS (e.g. mysql/postgres)
• sqlite (flat files, no daemon, flexible, but no concurrency)
• NoSQL - key-value store / document store (e.g. MongoDB, OrientDB)
• NoSQL - graph db (e.g. neo4j)

I think ArangoDB (wikipedia) looks very close to ringing most of the bells for what we're going to need to manage. From a high level, it's a nosql key-value document store with graph relationships built in and has its own relational query language (AQL). Python is well supported.

Take a look and see if you are into exploring this more or want to go with something we know better.

[geomat0101]

Arango Exploration Resources

• Our personal Arango instance - http://mediamgr.is-leet.com:8529/
• python-arango documentation
• Arango documentation
• Arango's interactive google colab notebooks (super cool stuff, we should do some of these)

[geomat0101]

Here are my initial thoughts on the data model