6 ms·
In every serious development the db architecture gets selected on the use cases specific to the business, so without describing which use cases HyperDex address
by alexro 15y ago
In every serious development the db architecture gets selected on the use cases specific to the business, so without describing which use cases HyperDex addresses there will be no real interest for it, name it 2.0 or "on steroids".
- rescrv 15y agoHyperDex provides strongly consistent GET/PUT operations and fast searches over data. It uses a new object placement technique to facilitate these searches, and as a result, a search may contact a very small subset of hosts in the system.
- alecco 15y agoThere's always a trade-off somewhere. Does it take 3x more RAM/storage? Does it make record insertion extremely slow?
- rescrv 15y agoTo tolerate f failures, we need to have f+1 replicas of the data. This implies increased storage, but the f parameter is entirely up to the application. Record insertion affects all replicas of the data, so latency increases with replication. The first graph on the performance page (http://hyperdex.org/performance/ http://hyperdex.org/performance/) shows that a 100% insertion workload will exhibit higher latency (and thus lower throughput for a fixed number of synchronous clients). Write-mostly workloads are slower, but I wouldn't say "extremely slow."
- alexro 15y agoFrom what I gather skimming through the paper, you should be more concerned comparing HyperDex to Riak, than to Cassandra or MongoDb. The potential use cases seem to be quite different for the last mentioned.
- tpsreport 15y agoIt's a consistent, scalable, high-performance key-value store. If you need the use cases spelled out for you, you should not be using it or anything else related to the web.