Libzdb is a database library with thread-safe connection pooling. The library can connect transparently to multiple database systems. It has zero runtime configuration and connections are specified via a URL scheme. A modern object-oriented API is provided. Libzdb supports MySQL, PostgreSQL, SQLite, and Oracle.
JumpBox for the MySQL Relational Database includes MySQL 5 along with PHPMyAdmin set up and ready to run. It's a great tool for developing database backed applications, and can also be used along with other JumpBoxes if you need to move the database into a separate virtual machine.
PostgreSQL is a powerful, open source object-relational database system that's been under active development for over 15 years. This JumpBox includes PostgreSQL 8 along with PHPPgAdmin set up and ready to run. The PostgreSQL server is network-accessible and provides a great storage engine for a broad array of applications.
iBeans aims to make integration for Web applications much easier than it is today. It does this by focusing on simplicity and task-based integration and avoids technical jargon and new concepts wherever possible. It offers easy to use integration for doing things like publishing and subscribing to JMS queues and topics, sending and receiving email, polling resources such as databases and ATOM feeds, task scheduling, creating HTTP/Rest services, consuming external services such as Amazon EC2 and S3, Twitter, Flickr, Google, and much more. It proves a Tomcat distribution that drops straight into Tomcat, with no need to mess with your project dependencies, and works with developer tooling for Tomcat or Tcat. It has a very simple API using annotations. This means iBeans can be plugged into your existing Web apps easily. It includes easy unit and mock testing using JUnit. IBeans Central offers a great place to discover and try new iBeans in your applications.
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.
Enrollix manages enrollment of people to associations, communities, groups, classes, teams, magazines, and events like meetings, parties, etc. It collects detailed personal data of members and of their enrollments (with a possible fee), selects them according to any kind of filter, and produces a balance of the revenues which can be saved in a CSV (comma separated value) file. This file can be opened with a spreadsheet like Calc or Excel. It is possible to prepare different models of certificates (like a receipt or a certificate of membership) within the software and print them with the data of any member, with a possible progressive number (like a protocol) within it. It can print labels of addresses or lists of payments of the selected (filtered) members, and it's possible to save their postal addresses or all their personal data in a CSV file, or to copy their email addresses to the clipboard, to paste them into the recipient field of a new message. The personal data of each member may contain a picture, which is saved in a directory with the same name and path of the file in use. It is possible to export selected members from the file in use to another Enrollix file, or to import all the members from it. Each member and his or her enrollments are internally identified by a unique mark (a UID number).
SqliteJdbcNG is a JDBC driver for SQLite. The overall goal of this project is to start a fresh implementation that leverages newly available technologies in the Java world. For example, any SQLite driver for any language must integrate with the native SQLite library. All of the current Java implementations rely on a custom JNI library to call out to the SQLite library. This extra layer can easily create a headache for the development and deployment of the driver, since it needs to be built for a variety of operating systems. Fortunately, there are technologies like Bridj and JNA that can be used to call native code directly from Java. By leaving the majority of the headaches of integrating with the native library to the Bridj project, more time can be spent on making a high quality driver that is more compliant with the JDBC4 spec.
PGObject::Simple::Role provides an interface to the PGObject service locator for Moo and Moose Perl classes. This service locator is intended to integrate Perl objects with PostgreSQL user-defined functions, and this uses the "simple" mapping approach. Between PGObject::Simple::Rrole and PGObject::Util::DBMethod, it is possible to write fully-declarative classes in which all calculation logic is handed off to database functions.