Continuent Announces New uni/cluster 2008 for PostgreSQL and EnterpriseDB

Posted on 2008-04-30

Continuent Announces New uni/cluster 2008 for PostgreSQL and EnterpriseDB

Advanced Database Replication and High Availability for Business-Critical PostgreSQL and EnterpriseDB Postgres Plus Database Applications

San Jose, CA – May 1, 2008 – Continuent, Inc., the leading provider of commercial open source middleware solutions for database high availability, today announced Continuent™ uni/cluster 2008. This newest version of Continuent's uni/cluster software provides the highest levels of availability and scalability for database applications built using PostgreSQL and EnterpriseDB™ Postgres Plus databases.

Continuent uni/cluster offers a multi-master approach to replication. Data is committed and available to all nodes in the cluster simultaneously, effectively eliminating data latency and providing increased reliability through redundancy. Continuent uni/cluster includes a build-in load balancer, which allows any database server to be used to process user queries, providing near-linear scalability, and optimal resource utilization, throughput and response time.

New features in Continuent uni/cluster 2008 include:

  • Simplified installation and configuration,

  • Faster performance by supporting for more than two cluster controllers,

  • Better management tools with new platform-independent Adobe® AIR™-based GUI, and

  • SUN Solaris™ support and Red Hat® 5 certification.

"I'm very glad to see uni/cluster now available on Solaris," said Josh Berkus, the leader of Sun Microsystems’ PostgreSQL team. "High availability is often the highest priority of our PostgreSQL for Solaris customers, and the new Uni/Cluster gives them another powerful tool for 99.999% uptime."

"We are pleased to have Continuent in our new Blade Partner Program," said Bob Zurek, CTO of EnterpriseDB. "Built-in failover and redundancy are essential in today's scale-out data centers that run Web 2.0 applications and demand unparalleled availability and scalability."

"With Continuent uni/cluster 2008, organizations have insurance against outgrowing the capacity of their system," said Eero Teerikorpi, CEO of Continuent. "They can add new database servers on the fly and take advantage of uni/cluster’s load balancing, where database activity is directed to the least busy server. This can be vital to maintaining continuous data availability for maximum productivity and meet customer expectations."

For more information about Continuent products, visit http://www.continuent.com. For information on Continuent's involvement in the open source community, visit http://www.continuent.org. More information about the Postgres Plus family of database products is available at www.enterprisedb.com.

About Continuent

Continuent provides continuous data availability. Continuent develops and markets commercial Continuent uni/cluster products and services based on Sequoia, a database-neutral, open source database-clustering project (www.continuent.org). Continuent’s commercial open source solutions are currently available for EnterpriseDB™, MySQL® and PostgreSQL. Continuent’s Sequoia open source solutions are available for Microsoft® SQL Server, Oracle®, IBM® DB2®, and Sybase®. Continuent is headquartered in San Jose, CA, with research labs in Finland and France. For more information, please visit www.continuent.com.

Press Contacts

pr@continuent.com

Adobe and Adobe AIR are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. EnterpriseDB is a trademark of EnterpriseDB Corporation. IBM and DB2 are registered trademarks of IBM in the United States. Microsoft is a registered trademark of Microsoft Corporation. MySQL is a registered trademark of MySQL AB in the United States and other countries. Oracle is a registered trademark of Oracle. Solaris is a trademark of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. Other products mentioned may be trademarks of their respective corporations.

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.