19 ms·
My first thought: Bigdis with a FUSE filesystem mapping to Amazon S3, you can have a huge database that's stored in triplicates, backed up, can be accessed from
by pierrefar 16y ago
My first thought: Bigdis with a FUSE filesystem mapping to Amazon S3, you can have a huge database that's stored in triplicates, backed up, can be accessed from anywhere, and scalable.
- antirez 16y agogood point IMHO, the idea of using the non exactly efficient encoding of one file per key is not just because the idea is based on large values, but also because this allows to exploit filesystem-level things. For instance if you happen to have a distributed filesystem running, the effect is to have a distributed DB.
- pierrefar 16y agoI've been thinking exactly along those lines for a while now. It started with me backing up MongoDB to S3 using one document = one S3 object. Each S3 stored document is a gzipped JSON string. From there, the idea of having a write through memory cache that saves to S3 is a quick leap, followed by allowing multiple servers to access the same S3 store. End result is a really eventually consistent scalable key=>document store. Yes I'm quite excited by Bigdis!