

(Session consistency is often ideal for scenarios where a device or user session is involved because it guarantees monotonic reads, monotonic writes, and read-your-own-writes.)

Some early choices made by the team included the following: It gave Skype everything needed for its new People Core Service (PCS), including turnkey global distribution and elastic scaling of throughput and storage, making it an ideal foundation for distributed apps like Skype that require extremely low latency at global scale. Skype found the perfect fit in Azure Cosmos DB, the globally distributed NoSQL database service from Microsoft.

The solution Putting data closer to users Note: Comments in italics/parenthesis are the author's. In part 3, we’ll cover the outcomes resulting from those efforts. In this post (part 2 of 3), we examine how Skype implemented Azure Cosmos DB to modernize its backend infrastructure. In part 1, we explored the challenges Skype faced that led them to take action. This is a three-part blog post series about how organizations are using Azure Cosmos DB to meet real world needs, and the difference it’s making to them.
