Continuent Finds Success Within SaaS Data Management Market

Posted on 2010-02-02

SAN JOSE, CA – February 2, 2010 – Continuent, Inc., a leading provider of solutions for continuous data availability, advanced database replication, backup and database performance scalability, today announced increased emphasis in the SaaS data management market in the wake of a number of new SaaS customer installations last year. As a result, Continuent will be focusing more on the data management market for SaaS, while continuing to offer high-availability solutions for ISVs, ISPs and Web 2.0 customers using PostgreSQL.

"The key needs of SaaS vendors include managing multi-tenant architectures with shared DBMS, maintaining customer SLAs for uptime and performance, and optimized, efficient operations," says Eero Teerikorpi, CEO at Continuent. "Our Tungsten solution has proven to be a very good match to cover these real money problems SaaS vendors are facing. Almost half of our customers in 2009 were SaaS vendors, and we expect this trend will not only continue but grow in 2010."

The key benefits Continuent Tungsten offers SaaS vendors are:

  • Meet customer SLAs by keeping applications available, not losing customer data and meeting response time requirements

  • Enable growth by easily adding more customers and covering the increased volume from existing customers, and providing new service offerings

  • Raise bottom-line profitability by keeping the cost of operation low and enhancing add-on revenue.

Tungsten offers high-availability, database cluster management and management of complex topologies for multi-tenant architectures.

Tungsten high availability and data protection features include maintaining live copies with data consistency checking and tightly coupled backup/restore integration with cluster management tools.

Tungsten cluster management allows SaaS vendors to migrate customers and perform system upgrades without downtime, thus enabling these maintenance operations during normal business hours.

Tungsten also enables complex replication topologies, including data filtering and data archiving strategies, maintaining extra data copies for data-marts, routing different customers to different DBMS copies, and providing cross-site multi-master replication.

As a commercial open source solution, Continuent Tungsten offers a cost-effective solution, matching other open source components and creating significant cost savings over commercial alternatives from Microsoft and Oracle.

For more information on Continuent Tungsten for SaaS solution, visit http://www.continuent.com or sign up for educational webcasts at http://www.continuent.com/news/webinars.

About Continuent

Continuent, the leading provider of data availability and database performance scalability solutions offers database high availability and incremental performance scaling using commodity hardware and databases. We provide continuous uptime so you can deliver business critical database applications with high data availability and accessibility. We also offer support, training and consulting services to our customers worldwide.

Continuent’s Tungsten provides a unique collection of solutions for database replication and cluster management. Tungsten’s core components are 100% open source. Tungsten is operating system independent and supports both commercial and open source databases including MySQL, PostgreSQL, EnterpriseDB and Oracle. For more information about Continuent and our products, visit www.continuent.com.

Press Contacts

pr@continuent.com This e-mail address is being protected from spambots. You need JavaScript enabled to view it

EnterpriseDB is a trademark of EnterpriseDB Corporation. Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. MySQL is a registered trademark of Sun Microsystems in the United States and other countries. Oracle is a registered trademark of Oracle. Solaris is a trademark of Sun Microsystems, 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.