Definition: Azure Cosmos DB is a fully managed, globally distributed, multi-model database service provided by Microsoft Azure. It is designed to offer high availability, low latency, and scalability across multiple regions with minimal configuration. Azure Cosmos DB supports multiple data models, including document (JSON), graph, key-value, and column-family models, and it provides APIs for working with various data types, including SQL (for document data), MongoDB, Cassandra, Gremlin (for graph data), and Azure Table Storage. Key Features: Global Distribution: Automatically replicates data across multiple regions with built-in support for global data distribution. Multi-Model Support: Offers flexibility by supporting document, key-value, graph, and column-family data models. Elastic Scalability: Can scale throughput and storage independently across regions to accommodate growing application needs. Low Latency: Ensures single-digit millisecond response times for read and write operations. Consistency Levels: Provides five tunable consistency models (strong, bounded staleness, session, consistent prefix, and eventual) to balance between consistency and performance. Fully Managed: Azure Cosmos DB is serverless and fully managed, meaning automatic backups, scaling, patching, and monitoring without manual intervention. Example: An example application of MongoDB is used to store the data transmited to central VIES in JSON. MongoDB is a JSON Native non-sql Database which optimizes the operations using this standard. Source: Microsoft Source reference: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-introduction Synonym: Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Central VIES is deployed on a cloud provider. The solution suggests using a managed kubernetes service for deploying most of the runtimes. The solution also requires file storage for backup files which are generated as part of the backup/restore service. VIES Solution requires a shared File System mechanism which is not attached to a particular instance/virtual machine, also does not require to support high throughput values in terms of i/o operations. Thus, Azure Files copes with this requirement. eira:iopDimension: Structural IoP LOST view: TVI-Central VIES Deployment Model eira:iopSaliency: File Storage ABB is salient for technical interoperability because it set up the data integration mechanism based on different files. This kind of file storage permit also ensures data provenance of the information considering file modification and creation. Identifier: http://data.europa.eu/dr8/AzureFilesTechnologyService eira:ID: http://data.europa.eu/dr8/AzureFilesTechnologyService ABB name: eira:FileStorageTechnologyService EIRA concept: eira:SolutionBuildingBlock Last modification: 29/04/2024