Utilizing a separate persistent datastore

[laurensdeb]

Using a persistent MongoDB or PostgreSQL database we could retain state on the information already parsed by the Parser as well as decouple the logic of our view and parsing in the long term.

• Investigate solutions for a datastore: Do we utilize a hosted service (MongoDB Atlas, Firebase, Heroku Postgres) or bootstrap something on a VPS?
• Write persisting logic for the current parser using an ORM
• Make the build step configurable to either pull data from the database for a certain session or to perform parsing and update the database as a whole.

Future steps:

• How to handle schema changes?
• How do we optimize builds to take advantage of these new features
• Strip the strict view code from the parsing & build logic and split this into a separate module
• Strip the model code from the parsing & build logic and split this into a separate module