SoftwareApplication
identifier: 10.5281/zenodo.8129516
name: dCache
description: dCache is a system for storing and retrieving huge amounts of scientific data, distributed among a large number of heterogeneous server nodes, under a single virtual filesystem tree with a variety of standard access methods including NFSv4.1 (pNFS), FTP, WebDav and xroot.
description: dCache is a distributed storage system providing location-independent access to data. The data are stored across multiple data servers as complete files presented to the end-user via a single rooted namespace. As the physical location of the data is not exposed to the user it can be migrated from one data server to another without interruption of service. Therefore the system can be expanded or contracted by adding/removing data servers at any time. dCache can be configured to work as a fast disk cache in front of tertiary storage systems. Such systems typically store data on magnetic tapes instead of disks, which must be loaded and unloaded using a tape robot. The main reason for using tertiary storage is the cost-efficiency of archiving a very large amount of data on less expensive hardware. Slower media or limited resources (like a number of tape drives) of tertiary storage systems lead to significantly higher access latency for archived data. dCache supports multiple data transfer protocols. The protocols are implemented as services that have modular deployment, allowing horizontal scaling by adding front-end machines without service interruption. Another performance feature of dCache is hot-spot data migration. In a situation when the rate of requests to read a file or a group of files is high resulting in a single data server or a group of data servers becoming "hot". If this happens dCache detects the condition and attempts to spread the load by distributing popular files to other, less busy, data servers. The flow of data within dCache can also be carefully controlled. This is especially important for large sites as the chaotic movement of data may lead to suboptimal usage. Instead, incoming and outgoing data can be marshaled so they use designated resources guaranteeing better throughput and improving end-user experience.
code repository: https://github.com/dCache/dcache
author: https://orcid.org/0000-0002-6217-8539
author: https://orcid.org/0000-0001-6733-2905
author: https://orcid.org/0000-0003-2825-0469
author: https://orcid.org/0000-0002-3957-1279
keywords: FAIR Data
keywords: data managment
programming language: Java
programming language: HTML
programming language: JavaScript
programming language: Shell
programming language: XSLT
programming language: CSS
programming language: Ruby
programming language: Roff
programming language: Less
programming language: Python
programming language: RobotFramework
programming language: AspectJ
programming language: Pascal
programming language: Dockerfile
programming language: sed
programming language: Makefile
programming language: BitBake
license:
  creative work: creativeWork
    name: AGPL-3.0-only
license:
  creative work: creativeWork
    name: BSD-Source-Code
license:
  creative work: creativeWork
    name: LGPL-2.0-or-later

https://orcid.org/0000-0002-6217-8539
type: Person
given name: Tigran
family name: Mkrtchyan
name: Tigran Mkrtchyan
role name: Project lead
affiliation: Organization
  name: DESY

https://orcid.org/0000-0001-6733-2905
type: Person
given name: Dmitry
family name: Litvintsev
name: Dmitry Litvintsev

https://orcid.org/0000-0003-2825-0469
type: Person
given name: Lea
family name: Morschel
name: Lea Morschel
affiliation: Organization
  name: DESY

https://orcid.org/0000-0002-3957-1279
type: Person
given name: Paul
family name: Millar
name: Paul Millar