ChronicDB Announces FREE Version And New Pricing

Online, June 1, 2010 (Newswire.com) - Along with this free version comes a new and improved pricing model that can better meet the needs of small consulting firms all the way up to enterprise software companies.

A key goal of ChronicDB is to eliminate the practice of unnecessarily establishing bi-directional replication. Bi-directional replication can be implemented at near real-time speeds, but it opens the possibility for data conflicts and consumes resources such as network bandwidth and storage. Although distributed asynchronous conflict resolution algorithms are known, parts of the conflict resolution logic must be manually written by users. In practice, developing conflict resolution code sometimes works and sometimes doesn't. In the cases where it doesn't, the database administrator must manually resolve the conflicts or ask the users to be continuously resolving them which are far from the desired mode of operation.

The technology is immediately available to be deployed throughout industries where even the smallest amount of downtime in a database can lead to huge profit loss and in some cases even the loss of human life. For example, the airline industry suffers substantial consequences when profits are lost due to database downtime. The same can be said for online ticketing sites as well as companies that thrive off of eCommerce. In the HealthCare industry, database down time can lead to serious miscommunication between doctor and patient. All these consequences are easily avoidable by integrating ChronicDB into database solutions.

ChronicDB has developed a way to completely eliminate the possibility of data inconsistencies while also eliminating the practice of unnecessary bi-directional replication, with zero database downtime. Fundamentally, replication is a technology suited for two use cases:

- Sharing data among databases that serve different purposes, such as periodically importing data from an Electronic Health Records system into a Billing system and vice versa. Under this use case fields in one database are only used for read access, as they are written only from the other database. There is no possibility of data conflict because the workflows of the applications do not conflict.
- Implementing high availability through hot-standby failover. A standby replica is maintained through near real-time replication, but if the replica is also treated as a second master copy, the possibility of data inconsistencies opens up again.

ChronicDB eliminates data inconsistencies by ensuring live database updates are atomic: a single master copy of a database is maintained at all times with replication applied to a single direction. Live database connections are migrated to an updated version of the database that is still the master copy.