The OpenLink Universal Data Access Driver Suite is a suite of high-performance drivers for ODBC, JDBC, OLE DB, and ADO.NET that enable development of database-independent applications. It supports OpenLink Virtuoso, Oracle, Microsoft SQL Server, Microsoft ACCESS, IBM DB2, Informix, Sybase, Ingres II, Progress, PostgreSQL, DBASE, Paradox, and other ODBC-compliant databases. It runs on x86, Itanium, Opteron, PPC, and Sparc, etc. platforms.
The c-tree Plus embedded database engine offers developers several APIs that provide low-level routines, ISAM-level control, and higher-level interfaces. c-tree Plus is distributed in complete C source, has been ported to 100+ environments and includes a robust database Server SDK. It can be used to develop single user and peer-to-peer applications, or the client-side for applications using FairCom's database server, the c-tree Server.
The c-tree Server is FairCom's multi-threaded, low-maintenance database server. It supports heterogeneous networks and lets dissimilar clients attach concurrently to any single or combination of c-tree Servers. Portability is afforded through over 30 supported platforms and 5+ supported communication protocols. c-tree Servers are easy to set up and require no system tuning or DBA. Additionally, FairCom offers a Server Side Development System, allowing developers to build their own application-specific database server.
Daffodil DB is a SQL-99 specification compliant, lightweight, Java-based relational database engine (RDBMS). It supports almost all constructs of SQL 99 (including triggers, views, constraints, UDT, stored procedures, etc.), supports distributed transactions (XA), provides a complete JDBC 3.0 driver (including support for optional features like save points, rowsets, UDT, XA, connection pooling, etc.), and can run in embedded or server mode. It can be included as a jar file in any Java application. Daffodil DB includes Daffodil DB Browser, a GUI-based database management tool that can be used to carry out all database operations such as creating a database, creating database objects, executing SQL statements, and manipulating data, browser database objects, etc.
HotCache is a transactional distributed caching system that runs on top of most RDBMSes. It provides an object-relational mapping tool that makes the use of embedded SQL unnecessary and saves tedious mapping programming. It enhances RDBMS commit functionality by adding commit-broadcast transactions where data is committed to the database and at the same time pushed to all other client caches, in essence keeping the data at remote clients hot. This improves performance by orders of magnitude (as most data access can be done locally) and reduces the load on the database server. The commit-broadcast transactions are implemented using UDP multicast for maximum network utilization. HotCache provides a sophisticated event framework that allows the client to register interest in business objects and be notified when changes are committed. The event framework is built so that it can be easily integrated with other systems' event-loops, eliminating multi-threading problems, etc. Notification can also be configured to take place in an asynchronous/multi-threaded method.
The eGenix mxODBC Zope Database Adapter (Zope DA) allows you to easily connect your Zope installation to just about any database backend. Unlike Zope's ZODBC Zope DA, the mxODBC Zope DA works on Windows, Linux, and Solaris using the same interface. It implements thread-safe connection pooling and multiple physical connects per logical Zope connection. You can safely run Z SQL Methods in parallel, achieving much better performance than ZODBC Zope DA or similar database adapters under heavy load. This makes it ideal for deployment in clusters and hosting environments where stability and high performance are a priority.
Itzam/C++ wraps the Itzam database engine with C++ templates for both simple and complex database classes. It supports B-tree, hash table, and sparse matrix indexes with unique or duplicate keys, and includes multithreaded resource locking and atomic file transactions. Complete class documentation is embedded in the source code, and available online and in the distribution archive.