[erlang-questions] kv store as a service
Sat Apr 5 18:02:07 CEST 2014
Amazon S3 and Riak are different species and actually not directly
comparable types in the nature of K/V world.
Question shows that you are not aware of usage types of these two and
you are not efficiently examined your problem domain by looking
closely to your data.
Please let us know more about your data types to be used.
What kind of data really you would like to store?
Why do you need cache?
Why do you believe SSD disks could be sufficient for cache operations?
What is your data access pattern in terms of retrieval of data back?
On Fri, Apr 4, 2014 at 3:10 PM, t x <txrev319@REDACTED> wrote:
> This is my current setup:
> * a bunch of $5/month digital ocean droplets 
> * these droplets have a 20GB SSD harddrive
> Now, I need to have a gigantic key-value store. I don't want to deal
> with the error condition of "error: you ran out of disk space"
> In my particular design, I only have "create new value". I don't
> have "update value". Thus, I don't have to worry about invalidating
> caches, and intend to use the 20GB SSD drives as as "cache" for the
> real key-value store.
> Now, my question is: what should I use for my key-value store?
> I want to optimize for:
> * minimum cost
> * minimum administration
> Currently, the best I have is Amazon S3. (I'd prefer to not setup my
> own Riak cluster + deal with replication + how many servers to run +
> ... ). I'm okay with the 99.99% (or whatever SLA Amazon S3 provides).
> Question: Is S3 the right approach as a giant K-V store for my
> Erlang nodes to hit, or should I be using something else?
>  This is not an advertisement for DO. I do not have any DO equity.
> erlang-questions mailing list
More information about the erlang-questions