DataStax

Interested in more talks like these? Register today for <a href="http://www.datastax.com/accelerate">Accelerate: A NoSQL Original Series</a>. We&rsquo;d love to see you online!
When Instagram was introduced all the way back in 2010, the social network stored all of its data in&nbsp;<a href="https://www.datastax.com/resources/definitions/what-is-apache-cassandra">Apache Cassandra&trade;</a> in a single data center located in the United States. As the company began to scale, they added a second data center to the mix. A little while later, they added a third.&nbsp;
Every time they added a new data center, they expanded replication.&nbsp;
Fast-forward to today, and Instagram serves 1 billion daily active users all over the world.&nbsp;
But to accommodate all of those users while maintaining high performance, they needed to adjust their data placement strategy.
&nbsp;
<h2>Cassandra on a global scale</h2>
At DataStax Accelerate 2019, Andrew Whang, an engineer at Facebook, explained how the company solved data placement challenges as it expanded.
<div><iframe src="https://www.youtube.com/embed/Sr0sX-TId-g" width="560" height="315" frameborder="0" allowfullscreen="allowfullscreen"></iframe></div>
&nbsp;
&ldquo;It became clear we needed to scale our hardware resources to support the increased workload,&rdquo; Whang explained. &ldquo;Ultimately, this meant more data centers in more countries.&rdquo;
Sure enough, Instagram added more data centers in other countries. But they realized that their replication strategy fell short at this scale.&nbsp;
When expanding to multiple countries, Instagram ran into two challenges:
<ul>
<li>Too many replicas: With three data centers, Instagram had three replicas. With five data centers, they had five replicas. This problem would only compound further over time.</li>
<li>Decreased performance: Quorum requests involved response from two replicas, located nearby one another. Over time, quorum requests required three replicas, and when they came from other continents, those replicas were not close to each other. This suboptimal configuration hurt performance.</li>
</ul>
&nbsp;
To solve these problems, Instagram decided to stop duplicating data everywhere. By only storing data closest to the region where it is generated, the company could build a faster, more efficient network that offered the performance benefits that come with local data access. After all, most users use Instagram from the same geographic region for the majority of the time.
By storing U.S. data in data centers based in the U.S. and European user data in data centers based in Europe, the company was able to achieve optimal performance.&nbsp;&nbsp;
Instagram also uses a tool developed by Facebook called <a href="https://engineering.fb.com/core-data/akkio/">Akkio</a> to manage local data at scale, delivering stronger user experiences because of it.
To learn more about Instagram&rsquo;s journey with Cassandra, how they overcame challenges, and the lessons they&rsquo;ve learned from it, check out Andrew&rsquo;s session from <a href="https://youtu.be/Sr0sX-TId-g">Accelerate 2019: Solving Optimal Data Placement for Instagram&rsquo;s Global Scale</a>.
&nbsp;

Accelerate Rewind: How Instagram Uses Cassandra to Operate on a Global Scale

DataStax

Share

Share

Cassandra on a global scale

More Success Stories

How PTC Is Transforming eCommerce with Generative AI, DataStax Astra DB, and Vector Search

LangChain and DataStax Astra DB Power Esynergy’s Retrieve-Augment Architecture for Sales Copilot

Vector Search in Action: How Restworld Improves Relevance and Accuracy in Job Matches

Restworld: Revolutionizing Hospitality Recruitment with Astra DB and Vector Search

One-stop Data API for Production GenAI