This link has been bookmarked by 1 people . It was first bookmarked on 26 Jun 2008, by Harjeet Singh.
-
26 Jun 08
-
At a high level the solutions can be split into two categories - file system interfaces to S3 or architecture based replication and backup.
-
FUSE Interfaces
- s3fs (Open Source)
s3fs is a FUSE filesystem that allows you to mount an Amazon S3 bucket as a local filesystem. It stores files natively and transparently in S3 (i.e., you can use other programs to access the same files). Maximum file size is 5G.
- PersistentFS (Closed Source, Current Development Version is Free)
PersistentFS is a fast and efficient POSIX-compliant file system that provides unlimited online storage in the Amazon Web Services (AWS) storage cloud.
- InfiniteFTP (Closed Source, Paid Service) over CurlFtpFs (Open Source)
- InfiniteFTP provides an FTP interface to Amazon S3 - while this isn't a file system approach then you could add a FUSE layer over the top to make it appear as one.
CurlFtpFS is a filesystem for accessing FTP hosts based on FUSE and libcurl.
NBD Interfaces
- ElasticDrive (Closed Source, Paid Service)
ElasticDrive is a Distributed Remote Storage Application that allows you to access your data regardless of location with the assurance your data is safe. It makes it possible for a remote storage resource, such as Amazon's Simple Storage Service (S3), Nirvanix & Xdrive to behave like a local hard drive.
-
Cost Considerations
I've only considered the options I could find for storage backed by S3 - my main in head reason for this was to avoid transfer charges. There will still be charges for the GET, PUT and LIST requests so I also need to consider the cost implications of using S3 to assist with persistent storage.
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.