Joachim Van Herwegen 1e1edd5c67 refactor: Clean up internal storage
Each IDP class using storage now has a different storage.
This way those classes don't have to worry about clashing keys anymore.

All internal storage is now in the /.internal/ container,
thereby making it easier to take the location of the internal data into account:
only 1 path needs to be blocked and a regex router handling internal data
differently only has to match 1 path as well.
2021-09-08 10:01:51 +02:00
..

Storage

Options related to how data and resources are stored.

Backend

The final part of the ResourceStore chain that handles data access.

  • dynamic: The routing store used here is needed when using dynamic pod creation.
  • file: Default setup with a file backend.
  • memory: Default setup with a memory backend.
  • regex: Uses a different backend based on the container that is being used.
  • sparql: Default setup with a SPARQL endpoint backend. Also updates the converting store so all incoming data is transformed into quads.

Key-Value

Used by certain classes for internal storage.

  • memory: Store everything in memory.
  • resource-store: Store everything in a specific container in the resource store.

Middleware

The chain of utility ResourceStores that needs to be passed through before reaching the backend stores. The final store in this chain takes the store from the stores/backend config as source.

  • default: Chains all the utility stores: Monitoring -> IndexRepresentation -> Locking -> Patching -> Converting