On Tue, Apr 08, 2014 at 02:12:58PM +0000, Lux, Jim (337C) wrote: > Consider something > like a credit card processing system. This is going to have a lot of "add > at the end" transaction data. As opposed to, say, a library catalog where > books are checked out essentially at random, and you update the "check > out/check in" status, and writes are sprinkled randomly through out the > data.
The way most NoSQL databases work, the library catalog would also do sequential writes. All updates, no matter where, are sequential writes. They're not your father's SQL database. -- greg _______________________________________________ Beowulf mailing list, [email protected] sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
