61–70 of 96 posts
I'm curious why you wouldn't include HBase as it's the dominant solution for NoSQL in systems requiring data consistency?
Only beacuse I don't know HBase very well. I'll read up on it, at least try it, and then add that too (and also maybe Tokyo Cabinet). Thanks for the feedback!
Both are schema free datastores. For me, this is the biggest, most useful difference between them and traditional SQL databases, because it makes things easy that are very, very hard (or inefficient) on an SQL database.
It's probably also worth noting that other NoSQL solutions don't share this advantage. For example, Cassandra requires all nodes to be restarted to apply a schema change, which can be quite a big deal.
Earlier quoted context omitted.
"The versioning system in couchdb is only there.." CouchDB does not version, period.
The "versioning" is really just there to support their optimistic concurrency model, if I recall. The idea is that you know you need to retry your operation if the version hash of the file has gone up since you last read the data and thus you know your local file is out of date. As I recall, the id field is just a string. It's just common to let it do the automatic "#-hash" representation. It's been a while since I p…
I'm curious why you wouldn't include HBase as it's the dominant solution for NoSQL in systems requiring data consistency?
Only beacuse I don't know HBase very well. I'll read up on it, at least try it, and then add that too (and also maybe Tokyo Cabinet). Thanks for the feedback!
Worth adding HBase? Much below Stolen from their overview page (All needs to be confirmed): http://hbase.apache.org/ WRITTEN IN: Java MAIN POINT: Hadoop Database LICENSE: Apache PROTOCOL: A REST-ful Web service gateway This project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. HBase is an open-source, distributed, versioned, column-oriente…
I'll question you on one point: "Use it when you need random, realtime read/write access to your Big Data." Does HBase now do a good job of random access? I was always under the impression that it did random access adequately, but it's real strength was with scans (based on ordering of keys).
I did benchmarks on a previous version, and the results were pretty miserable (600ms/lookup on a table with several million columns). It certainly sounds like they've improved.
Eg I have found out that deploying Tokyo Tyrant in a Rails project requires you to write some sčripts to ensure that things run properly. Also the db size has to be set in configuration in advance.
MongoDB OTOH is not designed for a single server environment, has a very small max document size, easily gets corrupted if process is stopped etc.
Apples vs Oranges vs Strawberries vs Pineapple vs Grapes Apples usually stay crispy unless baked. Good in pies. Oranges can be sour (or sweet). Do not bake. Strawberries are red. Good in pies, advise against baking. Pineapples are rough on the outside. Good fresh, baked, grilled, fried, debatable on pizza. Grapes come in many colors and sizes. Great fresh or turned into alcoholic beverages. (Not the worst introductio…
Actually, this would be useful and not superficial to someone who has seen pictures of these fruits but has never seen one in real life. Obviously it can be refined, but the idea is not bad. For example, try this with some quite different but seemingly similar fruits that most people are not as familiar with: Pineapple Guava (Acca Sellowania) -- Small green fruit. Seeds soft and edible, skin optional. Turpentine flav…
CouchDB & MongoDB both share one property that this comparison misses (or mentions only in passing). Both are schema free datastores. For me, this is the biggest, most useful difference between them and traditional SQL databases, because it makes things easy that are very, very hard (or inefficient) on an SQL database. It's probably also worth noting that other NoSQL solutions don't share this advantage. For example,…
That's no longer true. In 0.7, keyspaces and column families may be created, altered, or dropped live.
=== ( http://www.etradinglife.com ) ===
"Priority, my friend!! Christmas is coming, quick to our website shopping, our web site shopping there will be something different, unexpected things to you, let you have different sense, our website wholesale various fashion shoes, such as Nike, Jordan, prada, also includes the jeans, shirt, bags, hats and decoration. All these products are our free transport, prices are competitive, we can also accept paypal j, after the payment within short time, can ship. = New era cap $12;
Air jordan(1-24)shoes $30;
jordan air max oakland raiders $34a€“39;
Ed Hardy AF JUICY POLO Bikini $25;
Christan Audigier BIKINI JACKET $25;
Tshirts (Polo ,ed hardy,lacoste) $15
coogi DG edhardy gucci t-shirts $18;
gstar coogi evisu true jeans $35;
coach chanel gucci LV handbags $36;
Sunglasses(Oakey,coach,gucci,A r m a i n i) $15;
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
=== ( http://www.etradinglife.com ) ===
CouchDB & MongoDB both share one property that this comparison misses (or mentions only in passing). Both are schema free datastores. For me, this is the biggest, most useful difference between them and traditional SQL databases, because it makes things easy that are very, very hard (or inefficient) on an SQL database. It's probably also worth noting that other NoSQL solutions don't share this advantage. For example,…
"Cassandra requires all nodes to be restarted to apply a schema change, which can be quite a big deal." That's no longer true. In 0.7, keyspaces and column families may be created, altered, or dropped live.
Anyway, you still need a schema with Cassandra.