Table 1: Application of Distributed Storage Systems in Healthcare Application

System Storage Infrastructure Comments
Berkeley Ocean Store, UCLA Tapestry overlay for resource virtualization, FEC, location-independent routing abstraction Pro: Best suited for read-only archiving.
Con: prone to partitioning
Cooperative File System (CFS), MIT DHT DHash and Chord location protocol Pro: Decentralized, scalability
Con: File system layer only provides read-only file system semantics, no quota
Wuala, Swiss FIT DHT cipher-block chaining, Reed-Solomon FEC, Chord P2P overlay (super nodes, storage nodes and client nodes) Pro: provider archiving purposes, scalable, peers are both suppliers and consumers of resources, quota
BigTable, Google Google File System, DFS by SNA sharding Pro: scalable
Con: single master server, not distributed outside Google
Simple Storage Service, Amazon Zero-hop DHT, details unknown Pro: Excellent latency and scalability.
Con: Closed proprietary design

MIT, Massachusetts Institute of Technology; FIT, Federal Institute of Technology; UCLA, University of California, Los Angeles, SNA, shared nothing architecture, DHT, distributed hash table; FEC, forward error correction; DFS, distributed file system.