Hey there,
I just stumbled upon an interesting distributed db implementation. It's
designed to be ssd-backed, in-memory, nosql, thick-client, doc-store,
with secondary indexing. They have a good writeup on their architecture
and design choices.
http://www.aerospike.com/docs/architecture/index.html
https://github.com/aerospike/aerospike-server
http://highscalability.com/blog/2014/5/6/the-quest-for-database-scale-the-1-m-tps-challenge-three-des.html
Worth a read. The transaction rates they are claiming are scary, even
for beefy hardware.
-Daniel
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|