Ivan Pavlov's Library tagged databases →  View Popular

Flare is distributed, and persistent key-value storage compatible w/ memcached, and has more features (as follows):



• persistent storage (you can use flare as persistent memcached)
• pluggable storage (currently only Tokyo Cabinet is available, though:)
• data replication (synchronous or asynchronous)
• data partitioning (automatically partitioned according to # of master servers (clients do not have to care about it))
• dynamic reconstruction, and partitioning (you can dynamically (I mean, without any service interruption) add slave servers and partition master servers)
• node monitoring and failover (if any server is down, the server is automatically isolated from active servers and another slave server is promoted to master server)
• request proxy (you can always get same result regardless of servers you connect to. so you can think flare servers as one big key-value storage)
• over 256 bytes keys, and over 1M bytes values are available

How many times have you submitted a query to a database system, only to have it
go off in its own world, and leave no clue as to when you will get a result
back?

The goal of the ConEx project is to provide a framework for monitoring and estimating the progress of query execution in a database system.

Uzaygezen 0.1 is a space filling curve library with support for:

• Mapping from a multi-dimensional space into one dimension via the Compact Hilbert Index.
• The inverse mapping.
• Query building for databases with range query functionality, such as relational databases and more generally B-trees.
• Analysis support for read-only data to speed things up.