A survey and classification of software-defined storage systems

The exponential growth of digital information is imposing increasing scale and efficiency demands on modern storage infrastructures. As infrastructure complexity increases, so does the difficulty in ensuring quality of service, maintainability, and resource fairness, raising unprecedented performance, scalability, and programmability challenges. Software-Defined Storage (SDS) addresses these challenges by cleanly disentangling control and data flows, easing management, and improving control functionality of conventional storage systems. Despite its momentum in the research community, many aspects of the paradigm are still unclear, undefined, and unexplored, leading to misunderstandings that hamper the research and development of novel SDS technologies. In this article, we present an in-depth study of SDS systems, providing a thorough description and categorization of each plane of functionality. Further, we propose a taxonomy and classification of existing SDS solutions according to different criteria. Finally, we provide key insights about the paradigm and discuss potential future research directions for the field.This work was financed by the Portuguese funding agency FCT-Fundacao para a Ciencia e a Tecnologia through national funds, the PhD grant SFRH/BD/146059/2019, the project ThreatAdapt (FCT-FNR/0002/2018), the LASIGE Research Unit (UIDB/00408/2020), and cofunded by the FEDER, where applicable

Tiera: Towards Flexible Multi-Tiered Cloud Storage Instances

January 13, 2014attribute reaches a certain value, and (3) action events that occur when actions such as data insertion or deletion are performed. There are many responses that Tiera instances would eventually need to support. Table I shows some of the basic responses currently supported by our Tiera implementation: store data in a tier, retrieve data from a tier, move data between tiers, copy data from one tier to another, and delete data in a tier. Tiera also supports advanced responses: storeOnce, grow/shrink, compress/decompress, and encrypt/decrypt. Other responses that will be added to Tiera in the future include object versioning, journaling, transactions, and data snapshotting. Tiera’s design is highly modular making it very easy to add a new response 2. In Section II-C we will show how a rich array of data management policies can be easily constructed using these event-respons