Key-value Storage#
Key-Value Storage
|
status: draft
security:
safety: ASIL_B
|
||||
Feature flag#
To activate this feature, use the following feature flag:
experimental_kvs
Abstract#
This feature describes a key-value storage to be used within applications of the Eclipse S-CORE project, independent of the used application framework. It shall enable applications to access and store persistent data (primitive & non-primitive datatypes) associated with an unique key.
Motivation#
A key-value storage is used within many applications to store e.g. configuration data and is therefore seen crucial for the Eclipse S-CORE platform.
Rationale#
n/a
Specification#
Backwards Compatibility#
[Describe potential impact (especially including safety and security impacts) and severity on pre-existing platform/project elements.]
Security Impact#
[How could a malicious user take advantage of this new feature?]
Note
If there are security concerns in relation to the Feature Request, those concerns should be explicitly written out to make sure reviewers of the Feature Request are aware of them.
Safety Impact#
- Notes:
One key-value storage should not be used within different processes (freedom from interference) -> To be added to AoUs?
[How could the safety be impacted by the new feature?]
Note
If there are safety concerns in relation to the Feature Request, those concerns should be explicitly written out to make sure reviewers of the Feature Request are aware of them. ToDo - Link to the Safety Impact Method
[What is the expected ASIL level?] [What is the expected classification of the contribution?]
Note
Use the component classification method here to classfiy your component, if it shall to be used in a safety context: (TODO: add link to component classification).
License Impact#
[How could the copyright impacted by the license of the new contribution?]