For most users today, search is the primary means of file access. Despite this, search it typically implemented on top of older hierarchical namespace architectures. This project proposes to invert this relationship—building a file system for which the native naming convention is based upon search, and hierarchical names are merely one of many indexes into this search-based representation.
NetApp Faculty Fellowships (NFF) encourage leading-edge research in storage and data management and to foster relationships between academic researchers and engineers. Please see below for a current list of ATG’s NFFs.
Within cloud-based infrastructures, many applications can share a set of storage resources, and each application has its own service level objective that should be satisfied within this environment. As workloads change and applications are started, stopped, or moved, the load placed on the storage system changes. The storage system needs to automatically respond to these load changes by adjusting where data is stored and how it is serviced in order to continue to efficiently meet each application’s SLO.
How will ﬂash impact the next generation of parallel and distributed storage systems? One view is that the primary location for ﬂash in future systems is on the client side and not in the servers, which will remain disk-based. With ﬂash on the clients, and disks on the servers, the responsibilities and roles of storage are dramatically altered. First, ﬂash can decouple workloads from both network and server-side disk performance limits by serving as a large read cache and write buffer. Second, because data may persist in client-side ﬂash storage, redundancy must exist not only across server disks but also include client-side ﬂash. We call this arrangement, hierarchical redundancy.