This extension provides an API for communicating with Redis database,
a persistent key-value database with built-in net interface written
in ANSI-C for Posix systems.
It is a fork of alfonsojimenez's phpredis, adding many methods and
fixing a lot of issues.
This is a set of thin C++ wrappers for libgda v4 library.
This is a set of thin C++ wrappers for libgda v5 library.
SHA1, SHA256, SHA512, MD5 & CRC32 data types for PostgreSQL
A fork of the shatypes extension which adds additional
data types along with some fixes.
libhsclient is the client library of HandlerSocket for MySQL,
which is a NoSQL plugin for MySQL.
esqueleto is a bare bones, type-safe EDSL for SQL queries that works
with unmodified persistent SQL backends. Its language closely resembles
SQL, so you don't have to learn new concepts, just new syntax, and it's
fairly easy to predict the generated SQL and optimize it for your
backend. Most kinds of errors committed when writing SQL are caught as
compile-time errors---although it is possible to write type-checked
esqueleto queries that fail at runtime.
libmemcached is a C and C++ client library to the memcached server
(http://danga.com/memcached). It has been designed to be light on memory usage,
thread safe, and provide full access to server side methods.
A few notes on its design:
# Synchronous and Asynchronous support.
# TCP and Unix Socket protocols.
# A half dozen or so different hash algorithms.
# Implementations of the new cas, replace, and append operators.
# Man pages written up on entire API.
# Implements both modulo and consistent hashing solutions.
It also implements several command line tools:
memcat - Copy the value of a key to standard output
memflush - Flush the contents of your servers.
memrm - Remove a key(s) from the serrver.
memcp - Copy files to a memached server.
memstat - Dump the stats of your servers to standard output
memslap - Generate testing loads on a memcached cluster
Riak is a distributed database designed for maximum availability:
so long as your client can reach one server, it should be able to
write data. In most failure scenarios the data you want to read
should be available, albeit possibly stale.