---
title: "replication | Skills We Assign For | Azendo"
description: "Database replication — read scaling, failover and replica lag, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/replication/"
---

[Skills](https://azendo.co/skills/) Data stores and query 

# replication.

Replication maintains copies of a database on other servers, for read scaling, high availability or geographic proximity. It is synchronous or asynchronous, and that choice decides the trade between consistency and latency.

## Where replication fits on a long engagement.

Replica lag is the thing applications get wrong. A write to the primary followed immediately by a read from a replica may not see it, which produces the classic defect where a user saves something and it appears not to have saved. The application has to decide, per read, whether it can tolerate slightly stale data.

Failover is the other half and is frequently untested. Promoting a replica involves the promotion itself, redirecting applications, and handling any writes the old primary accepted but did not replicate. A failover procedure that has never been exercised is a plan, not a capability.

## What an assigned team does with replication.

Replication is usually introduced for read scaling and then quietly relied on for availability, without the failover work that assumption requires. The gap is discovered during the incident it was supposed to protect against.

Testing failover deliberately is ordinary operational rigour, held by the assigned capacity as part of the standards described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use replication for.

* Read load moved off the primary Reporting and analytics served from replicas, with staleness tolerance decided per read.
* Failover that has been exercised Promotion tested, so availability is a capability rather than an assumption.
* Lag monitored and acted on Replica delay alerted, because a lagging replica silently serves old data.

## How replication capacity is assigned.

Replication work is assigned under [managed data services](https://azendo.co/services/data-engineering/), with failover tested rather than documented.

## Roles we assign replication for

* [Database Administrator Data engineering](https://azendo.co/services/data-engineering/database-administrator/)

## Service lines it sits in

* [Data engineering](https://azendo.co/services/data-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in data stores and query

* [SQL — skill we assign for](https://azendo.co/skills/sql/)
* [PostgreSQL — skill we assign for](https://azendo.co/skills/postgresql/)
* [MySQL — skill we assign for](https://azendo.co/skills/mysql/)
* [MongoDB — skill we assign for](https://azendo.co/skills/mongodb/)
* [Snowflake — skill we assign for](https://azendo.co/skills/snowflake/)
* [BigQuery — skill we assign for](https://azendo.co/skills/bigquery/)
* [Redis — skill we assign for](https://azendo.co/skills/redis/)
* [Prisma — skill we assign for](https://azendo.co/skills/prisma/)

## Tell us what your roadmap needs replication for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)