Abstract

Across the years, being the backbone of numerous data management solutions used within the WLCG collaboration, the XRootD framework and protocol became one of the most important building blocks for storage solutions in the High Energy Physics (HEP) community. The latest big milestone for the project, release 5, introduced multitude of architectural improvements and functional enhancements, including the new client side declarative API, which is the main focus of this study. In this contribution, we give an overview of the new client API and we discuss its motivation and its positive impact on overall software quality (coupling, cohesion), readability and composability.

Highlights

  • The XRootD [1] project aims at providing low latency and scalable data access for large scientific data sets and is based on a scalable, plug-in centric architecture and a communication protocol

  • For almost 10 years the XRootD framework has been very successful at facilitating data management of LHC experiments and grew into one of the most important storage technologies in the High Energy Physics (HEP) community

  • It comes with no surprise that XRootD development is largely driven by the use cases coming from the WLCG project, as it is the backbone of numerous software defined storage solutions used to accommodate the vast amount of data registered by the LHC experiments at CERN, most notably Atlas [4], CMS [5], LHCb [6] and Alice [7]

Read more

Summary

Introduction

The XRootD [1] project aims at providing low latency and scalable data access for large scientific data sets and is based on a scalable, plug-in centric architecture and a communication protocol. It has been designed with particular emphasis for geographically distributed, file-based repositories. It comes with no surprise that XRootD development is largely driven by the use cases coming from the WLCG project, as it is the backbone of numerous software defined storage solutions (like EOS [2] and DPM [3]) used to accommodate the vast amount of data registered by the LHC experiments at CERN, most notably Atlas [4], CMS [5], LHCb [6] and Alice [7].

The Object Oriented APIs
Executing a pipeline
Forwarding values between handlers and operations
Control directives
Cyclomatic complexity
Cohesion
Coupling
Findings
Conclusions
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.