CacheGuard Appliance is an all-in-one OS appliance providing firewall, antivirus, caching, compression, bandwidth allocation, load balancing, reverse and forward proxy, high availability, Web application firewall, URL guarding, and more. It can be purchased as an OS to install on your server, as an OS to run in a virtual machine, or as a hardware appliance.
Moose File System (MooseFS / MFS) is a fault tolerant, network distributed file system. It spreads data over several physical servers, which are visible to the user as one resource. For standard file operations MooseFS mounted with FUSE acts like other Unix-alike file systems: it has a hierarchical structure; it stores POSIX file attributes; and it supports special files, symbolic links, and hard links. Access to the file system can be limited based on IP address and/or password. It offers high reliability, since several copies of the data can be stored across separate computers. Capacity is dynamically expandable by attaching new computers or disks. Deleted files are retained for a configurable period of time (with a file system level "trash bin"). MooseFS supports coherent snapshots of files, even while the file is being written or accessed.
Galera wsrep provider is a dlopenable generic replication library which implements the wsrep provider API. It provides very efficient synchronous replication, and multi-master and "parallel applying" capabilities for opaque data buffers. Its primary focus is data consistency. A transaction is either committed on every node, or not at all. It works anywhere TCP works, including on WAN, and can utilize UDP multicast where available. It is used by the MySQL-wsrep patch project to create true multi-master MySQL/InnoDB clusters.
Shinken is an advanced monitoring system that is based on Nagios, but redesigned and rewritten from scratch while maintaining compatibility. It can monitor all IT devices from systems to end user applications. In case of a failure, Shinken can alert the operation engineers so they can promptly repair it. It has the same capabilities as Nagios along with more advanced built-in facilities such as load balanced and high availability monitoring.
Hados stores files in a cluster of servers. Its goal is to handle high availability by storing copies of the same file on several nodes. It provides RESTFUL APIs to easily store, check, or retrieve files. Using the cluster APIs, you can retrieve files from whichever node hosts them. To avoid any single point of failure, it is possible to apply a request to any node of the cluster; there is no master node.
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.
CExpert (Connection Expert) is a simple library that allow high-availability projects to check their mysql base's health. It consists of two parts a daemon and a client library. The CExpert daemon is a light process that periodically checks MySQL's health and reports it to all clients interested. Communication between processes is implemented using POSIX shared memory, so reading health status is simply a matter of checking one memory byte.
Hades is a high availability (HA) data source. This HA data source contains two other data sources: the main one and the failover one. The HA data source exposes one of them at a time and can automatically switch between them when certain conditions are met. These conditions are highly configurable. By default, when the main data source is overloaded, the failover data source is used. The load of a data base is determined on the basis of the average execution time of some configurable SQL statement that is examined periodically. The HA data source exposes through JMX its state and also operations for manual switching between the two contained data sources in case automatic switching must be suppressed for some reason.