3 ms·
What sort of faults and how much tolerance? What levels of consistency, availability and partition tolerance? How small is 'small?' Or to put it another way,
by brudgers 10y ago
What sort of faults and how much tolerance?
What levels of consistency, availability and partition tolerance?
How small is 'small?'
Or to put it another way, what are you trying to do?
What latency is acceptable?
- ffggvv 10y agoStoring information about users. There won't be many 1000-5000. The data should be replicated on at least two small servers.
- brudgers 10y agoAll the other questions are still relevant. I mean if the latency is acceptable, Amazon S3 could store the file and is probably more reliable for handling replication as a backup strategy than anything most developers could implement themselves on hardware under their control...actually, I'm thinking a 'cloud' approach is probably the most robust generic strategy and a service like AWS provides good documentation and self-help support and has a rich third party ecosystem. Pay for what you use pricing can be issue, but at a small scale it's often cheaper than alternatives because usage is low and there's no minimum. Anyway, absent information facilitates absent specificity.