Notes for data storage interface

The data storage interface will need the following operations:

• Set a new K/V pair
• Read a new K/V pair

What types of data will be supported? Should the interface care? (yes, anything stored to the data storage needs to be serializable to/from JSON)

How to prevent namespace collisions or malicious overrides? Should data be namespaced? What happens at runtime if a user installs two mods that conflict? Who gets priority? How can we verify the original owner?

How can other models integrate with the data store?

Will also need an event handling model that interacts with the datastore.

Datastore: contains the current state of data

Datastore Clients:

• Event handling (polling and pushed updates) [Event handling will need its own module]
• Webserver (reads data from datastore to craft responses)