Tsung is a distributed load testing tool. It is protocol-independent and can currently be used to stress HTTP, WebDAV, PostgreSQL, MySQL, LDAP, AMQP, and XMPP/Jabber servers. It simulates user behavior using an XML description file, reports many measurements in real time (statistics can be customized with transactions, and graphics generated using gnuplot). For HTTP, it supports 1.0 and 1.1, has a proxy mode to record sessions, supports GET, POST, PUT, and DELETE methods, cookies, and basic/digest authentication. It also has support for SSL, WebSocket, and BOSH.
hamsterdb Embedded Storage is an embedded database engine for C/C++, including wrappers for Java, .NET, and Erlang. It supports in-memory databases, very fast database cursors, "record number" databases, ACID transactions, and duplicate keys. hamsterdb is very fast and highly configurable. It compiles and runs on Unix platforms, Linux, Microsoft Windows, and embedded platforms.
VoltDB is a blazingly fast relational database system. It is specifically designed to run on modern scale-out architectures: fast, inexpensive servers connected via high-speed data networks. It is aimed at a new generation of database applications - real-time feeds, sensor-driven data streams, micro-transactions, low-latency trading systems - requiring database throughput that can reach millions of operations per second. What’s more, the applications that use this data must scale on demand, provide flawless fault tolerance, and enable real-time visibility into the data that drives business value. It includes client application drivers for applications written in Java, C++, C#, PHP, and Python. VoltDB community members have also authored client libraries for Erlang, Ruby and Node.js. There are streaming export capabilities for leading analytic database environments, including Apache Hadoop.
epers stands for "Erlang persistence". As the name suggests, it tries to make it easy to use databases in Erlang programs, to make the language a little more agile, and (humbly) offer a nice adapter for several databases, hiding their implementation details (and the API of the library/framework/driver used to communicate with them). To achieve this, it aims to offer a somewhat consistent API to define and work with your model, while at the same not coupling your code too tightly to it.