Cybertec Schönig & Schönig GmbH, one of the
world's leading PostgreSQL companies, today announced the
availability of Cybercluster 2.0, a synchronous single-master replication solution
for PostgreSQL 9.0.
Cybercluster 2.0 is completely based on PostgreSQL's internal Write Ahead Log
(WAL) and thus offers highest possible performance at minimal overhead.
Cybercluster 2.0 will seaminglessly integrate into existing PostgreSQL
installations and it is 100% compatible with PostgreSQL 9.0.
How does it work?
Cybercluster 2.0 offer synchronous replication. This means that a transaction is
only marked as committed if it has safely been replicated to your entire
database cluster. There is no chance of losing a transaction anymore - even if a
database node in your cluster dies you can rely on the fact that no data can
ever be lost. Your cluster will always stay consistent and ready to serve your
business.
Cybercluster 2.0 uses PostgreSQL's Write Ahead Log and efficiently streams data
to all nodes in the cluster. You can flexibily choose if you want to replicate
synchronously or asynchronously to an array or database slaves. You can even mix
synchronous and asynchronous replication - this guarantees unprecedented
flexibility, enhanced stability and superior replication performance.
Support
Cybertec Schönig & Schönig GmbH provides full 24x7 support for Cybercluster 2.0
and offers a stable upgrade path to future versions of PostgreSQL.
Cybercluster can be used with all platforms which are known to work with
PostgreSQL 9.0. This includes but is not limited to Linux, Mac OS X, FreeBSD as
well as Microsoft Windows XP / Vista / 7.
Get Cybercluster 2.0
You can find more information about Cybercluster 2.0 on our website:
About Cybertec:
Cybertec Schönig & Schönig GmbH has provided professional database services for
more than 10 years and we are an active contributor to the PostgreSQL community.
We have been working with customers worldwide.
Contact:
Cybertec Schönig & Schönig GmbH
Reyergasse 9 / 2
A-2700 Wiener Neustadt
Web: www.cybertec.at
This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.