Integrate a New Parameter Storage Backend

[SterlingPeet]

Pattern

Describe how to create a new storage backend for storing parameters.

Rationale

Sometimes there are different storage requirements or features that are required for a mission's parameter storage. Perhaps there is no file access, and the parameter database needs to leverage non-volatile EEPROM. Or perhaps the QA team needs to be able to access stored parameters to enhance their tests. Describing this pattern enables mission developers to solve parameter storage problems faster.

[timcanham]

Good one! We've done this internally, but never described the pattern.

[SterlingPeet]

An additional thought: I have seen a scenario where a deployment was stored in a location where filesystem changes could not be made (its an odd requirement, but it was true nonetheless), but a different deployment on the mission was able to store parameter data. A memory-only parameter database cache that tries to get parameters from the other deployment via a hub, would be an interesting recipe to describe. In this case, the requirements to consider where the other database is not guaranteed to exist or be accessible would be interesting however I would leave the concrete implementation of this case as an exercise for the reader.