Architecture#
Persistency KVS Feature Architecture
|
status: valid
security: NO
safety: ASIL_B
|
||||
Overview#
The Key-Value-Storage (kvs) provides the capability to efficiently store, retrieve, and manage key-value pairs in a persistent storage system.
Description#
kvs organize data as pairs, where each unique key is associated with a specific value. The key acts as a unique identifier for getting the value.
The data is persisted in JSON format to the file system, providing a human-readable, and widely supported way to store and manage key-value pairs.
The JSON data persisted is according to RFC-8259.
Rationale Behind Architecture Decomposition#
The architecture is decomposed to include a dedicated JSON parser component (json) to facilitate the persistent storage of data in JSON format.
The architecture is decomposed to include a FileStorage component (fs) to read and write to the file system.
Glossary#
User: Program code that is written by a person that initiates the given functionality call or receives a callback.
Static Architecture#
Static Architecture
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Dynamic Architecture#
Check if key contains default value
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Delete key from KVS instance
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Flush to permanent storage
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Read key value
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Read data from permanent storage
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Write value to key
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Restore snapshot
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||
Logical Interfaces#
Ikvs
|
status: valid
security: YES
safety: ASIL_B
|
||||
|
|||||