Object data storage

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.

1. General description

Registry data management subsystem uses the Ceph object storage of the Subsystem for distributed data storage for storing data and their digital signatures when entering the register, files of digital documents and data for transmission during inter-service interaction.

A bucket for storing data and their digital signatures when entered in the register.

Object key generation pattern

$UUID

Table 1. Description of the structure of the JSON document for storing the system signature
Attribute (JSON-path)	Data type	Description
`signature`	String (Base64)	Digital seal
`data`	JSON Object	The signed data structure

Table 2. Description of the structure of a JSON document for storing a user request to change registry data
Attribute (JSON-path)	Data type	Description
`signature`	String (Base64)	User QES
`data`	JSON Object	The signed data structure
`x-access-token`	String	JWT token of the user who signed the data

Table 3. Description of the structure for checking the integrity of messages during interservice interaction
Data type	Description
String (Base64)	A digital stamp is placed on a message during inter-service interaction

A bucket for storing digital registry documents.

Object key generation pattern

$UUID

Table 4. Structure description
Data type	Description
byte[]	The contents of the registry file

A bucket for temporary storage of data for transfer as part of interservice interaction.

Object key generation pattern

datafactory-$UUID

Table 5. Description of the structure of the JSON document for storage
Attribute (JSON-path)	Data type	Description
`payload`	JSON Object	A data structure representing the result of a request
`status`	String (Enum)	Operation status
`details`	String	A detailed description of the operation status