From 294c31ef38d03a551cc7adc080eb8b3d072831af Mon Sep 17 00:00:00 2001
From: Alban Perillat-Merceroz <A21z@users.noreply.github.com>
Date: Tue, 23 Feb 2021 10:44:43 +0100
Subject: [PATCH] Add "Scaling your on-duty team" blog post by Teads
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Abstract of the article:

> The internet never sleeps, and even with the best design for resilience, one day, your system will go down.
At Teads, we deliver outstream video advertising for the biggest content publishers in the world. Any downtime has important repercussions on our revenue but also on the publisher’s revenue.
In a few years we grew from a start-up to a scale-up, although we operate globally, our tech team is mostly based in France. For this reason, we decided to carefully think about scaling our on-duty team in order to minimize the downtime when a system goes down.
---
 README.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/README.md b/README.md
index c3d1857..99bb15d 100644
--- a/README.md
+++ b/README.md
@@ -824,6 +824,15 @@ _Note to readers: This list refers to some of the articles, posts, videos, tools
 
 </details>
 
+<details>
+  <summary>Teads</summary>
+
+### Blog Posts
+
+* [Scaling your on-duty team](https://medium.com/teads-engineering/scaling-your-on-duty-team-bc467c480747)
+
+</details>
+
 <details>
   <summary>Trivago</summary>