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.
HOMER is a robust, carrier-grade, scalable SIP capturing system and monitoring application with hEP, IP Proto4 (IPIP) encapsulation, and port mirroring/monitoring support right out of the box, ready to process and store large amounts of signaling with instant searches, end-to-end analysis, and drill-down capabilities for ITSPs, VoIP providers, and trunk suppliers using SIP signaling.
cola is a C implementation of the COLA structure described in the paper "Cache Oblivious Streaming B-Trees" by Bender, Farach-Colton, et al. This algorithm is a drop-in replacement for B-Tree databases/indexes which performs faster on spinning disks than B-Trees do on SSD. It's asymptotically optimal in terms of data transfers to and from disk. For example, random key inserts are turned into linear sequential writes while maintaining the property which queries always require, at most, precisely log N blocks read sequentially (but not contiguously) from disk (or half that, on average).
Bibfilex is software to create and manage archives of bibliographical items (books, articles, etc.) according to Biblatex structure and rules. It is far less advanced than other bibliographic managers like JabRef, and allows only a few customizations. Its strength is speed and lightness, especially when used with many items. It uses SQLite as a database. It can store the items according to each of the entry types described in the Biblatex manual (book, article, etc.), import the content of a file in Biblatex format (like a JabRef database, a Mendeley BibTex exported file, or a Google Books BibTex downloaded file), export data to a Biblatex file (like a JabRef database), locate an item just typing its author name, title, etc. filter the items by selecting a keyword in a list, filter the items according to three different conditions (or to manually modify the SQL statement of the filter to make it more suitable or complex) or according to the \cite commands contained within a Latex document, associate various attachments (files of every kind) with each item, activate autocompletion of data in each field with “Ctrl + Space”, automatically create unique BibTex keys according to a pattern defined by the user, and specify the fields (columns) shown in the grid view of the data. It is also possible to replace the \cite and \printbibliography commands in a Latex document with extended citations and bibliography, which are composed according to a user-defined pattern, to export the Latex file in other formats more easily.
LMDB is an ultra-fast, ultra-compact key-value data store developed by Symas for the OpenLDAP Project. It uses memory-mapped files, so it has the read performance of a pure in-memory database while still offering the persistence of standard disk-based databases, and is only limited to the size of the virtual address space (it is not limited to the size of physical RAM).
STK/Unit is a pure SQL testing framework for MariaDB and MySQL. Users can create Base Tests (Stored Procedures) which are part of Test Cases (databases) and, optionally, Test Suites (other Stored Procedures). Output is stored in internal tables. You can convert it to a human-readable string, valid HTML, or query some convenient views which group results. It can be used to test any SQL structure (tables, views, triggers, stored routines), as well as server upgrades or configuration changes.