database replication

Database replication becomes difficult when it scales up.

Sometimes database replication may be involved as a method of copying data between databases - and this can significantly slow down the whole process.

Jet 3.0 also allowed for database replication.

Database replication can be used on many database management systems, usually with a master/slave relationship between the original and the copies.

Database replication, where copies of data on a database are kept in sync, despite possible large geographical separation.

Besides distributed database replication and fragmentation, there are many other distributed database design technologies.

As Wikipedia grew, achieving scalability through multiple layers of caching and database replication became a major concern for the developers.

In database replication, the master database is regarded as the authoritative source, and the slave databases are synchronized to it.

The "scope" can be anything from full database replication to something as fine grained as anything definable by a Versant query.

Versant Async Server: Production Database Replication.

The eXtremeDB high availability edition supports both synchronous (2-safe) and asynchronous (1-safe) database replication, with automatic failover.

A replication is extendable across a computer network, so the disks can be located in physically distant locations, and the master-slave database replication model is usually applied.

Nearly universal at one time, it is now becoming less popular in favor of the use of other database replication mechanisms that modern DNS server packages provide.

Multi-master replication is a method of database replication which allows data to be stored by a group of computers, and updated by any member of the group.

It included database replication, providing cluster-wide replication and fail-over within/across data centers (VoltDB Enterprise Edition only).

The PostgreSQL database system also uses WAL to provide point-in-time recovery and database replication features.

Enterprise level geodatabases support database replication, versioning and transaction management, and are cross-platform compatible, able to run on Linux, Windows, and Solaris.

Compared to database replication, log shipping does not provide as much in terms of reporting capabilities, but also backs up system tables along with data tables, and locks standby server from users' modifications.

MediaWiki supports Squid, load-balanced database replication, client-side caching, memcached or table-based caching for frequently accessed processing of query results, a simple static file cache, feature-reduced operation, revision compression, and a job queue for database operations.

Though it is standardized, full-zone transfer being described as one of the possible database replication mechanisms in RFC 1034 (incremental zone transfer described in RFC 1995), zone transfer is the most limited of those database replication mechanisms.

Fortunately, for this and several reasons outlined later, DNS servers that use such sophisticated database back ends in general rarely use zone transfer as their database replication mechanism in the first place, and usually instead employ the vastly superior distributed database replication mechanisms that the back ends themselves provide.