Possible scopes, from highest to lowest priority:

• One semi-technical, high-level overview and impact of multi-DC
  • target audience: entry-level engineers and non-technical audience, people from other organizations looking to answer the question "my company is facing a similar challenge, how should I proceed? What can I learn from their experience?"
  • Content: What motivated Multi-DC?, How did we have to change how we think. Why are we in a better state now? What kind of incidents are we able to prevent in the current state? What did we learn? Nutshell overview of main changes (cross dc TLS, mcrouter, ATS routing, circular MainStashDB replication)
• One in-depth technical post, educational in nature.
  • audience: entry-level engineers, tech audience.
  • Content: focus on a particular change needed to the stack for multi-dc (WANCache, MainStash, RDBMS)
• Performance impact and logged-in user
  • audience: entry-level engineers, non-perf experts
  • Content: Motivation, Performance impact expected, performance impact observed, how it was measured, learnings
  • General population impact due to distance. Cache miss Singapore

Let's focus on the strategic impact and on the educational one first.