otis's Feed

tokyotyrant-java - Google Code

otis — Thu, 25 Jun 2009 02:56:00 -0400

Tagged by otis under keys, hash table, client, java, library, software, database,

schemafree - Google Code

otis — Tue, 09 Jun 2009 04:49:00 -0400

Schemafree is a key/value store based on Mysql Tagged by otis under database, hash table, keys, values, mysql, store,

Performance comparison: key/value stores for language model counts - Brendan O'Connor's Blog

otis — Wed, 03 Jun 2009 02:00:00 -0400

Tagged by otis under hash table, keys, database, performance, report, compare,

Flare is distributed, and persistent key-value storage

otis — Fri, 29 May 2009 05:12:00 -0400

Tagged by otis under keys, values, storage, database, server, hash table, memcached, distributed filesystem,

repcached - add data replication feature to memcached

otis — Tue, 26 May 2009 02:53:00 -0400

Tagged by otis under keys, values, storage, database, server, hash table, memcached,

nmdb - A multiprotocol network database

otis — Tue, 26 May 2009 02:52:00 -0400

nmdb is a network database (dbm-style) for controlled networks that can use different protocols to to communicate with its clients. It supports TIPC, TCP, UDP and SCTP. It consists of an in-memory cache that saves (key, value) pairs, and a persistent backend that stores the pairs on disk. Both work combined, but the use of the backend is optional, so you can use the server only for cache queries, pretty much like memcached. Tagged by otis under keys, values, storage, database, server, hash table,

Anti-RDBMS: A list of distributed key-value stores | Richard Jones, Esq.

otis — Tue, 26 May 2009 12:44:00 -0400

Tagged by otis under keys, values, database, hash table, storage, review,

Plurk Open Source - LightCloud - Distributed and persistent key value database

otis — Tue, 26 May 2009 12:42:00 -0400

Distributed and persistent key-value database Tagged by otis under keys, values, database, hash table, server, api, distribute, storage,

redis - Google Code

otis — Tue, 26 May 2009 12:40:00 -0400

Redis is a key-value database. It is similar to memcached but the dataset is not volatile, and values can be strings, exactly like in memcached, but also lists and sets with atomic operations to push/pop elements. Tagged by otis under keys, values, database, hash table, server, api,

Tokyo Tyrant: network interface of Tokyo Cabinet

otis — Tue, 26 May 2009 12:37:00 -0400

Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet. Though the DBM has high performance, you might bother in case that multiple processes share the same database, or remote processes access the database. Thus, Tokyo Tyrant is provided for concurrent and remote connections to Tokyo Cabinet. It is composed of the server process managing a database and its access library for client applications. Tagged by otis under keys, values, database, hash table, server, api,

SubRecord - Enterprise Aspects Stack - storage/logging/tracing/metrics/security/monitoring infrastructure

otis — Fri, 27 Feb 2009 03:11:00 -0500

Tagged by otis under keys, values, hash table, logging, log analysis, storage, hbase, solr, lucene,

Project Voldemort

otis — Sun, 25 Jan 2009 11:59:00 -0500

Voldemort is a distributed key-value storage system Tagged by otis under distributed computing, hash table, keys, values,

Memcachedb: A distributed key-value storage system designed for persistent

otis — Mon, 03 Dec 2007 03:53:00 -0500

Memcachedb is a distributed storage system designed for persistence. We simply hacked from memcached and tugela. But neither of them. Memcachedb is not a cache solution, it is a persistent solution for high-frequency writing and reading. It conforms to memcache protocol(not completed, see below), so any memcached client can have connectivity with it. Memcachedb uses Berkeley DB as a storing backend, so lots of features including transaction and replication are supported. Tagged by otis under database, performance, distribute, hash table, keys, values, store, bdb,