The article explains that Lync (Skype for Business) Server relies on several SQL Server instances—including CMS, RTC, and Rtcdyn—distributed across front‑end and back‑end servers, using push replication from a master to ensure data consistency and high availability, and discusses deployment considerations for standard versus enterprise editions.
The article explains 58.com’s service‑oriented architecture that combines dual‑master MySQL replication, a standby database, and Redis caching to provide high‑availability read/write operations, outlines their scaling process, and details a four‑step cache‑consistency strategy.
The article explains how startup engineers can design and evolve a scalable web architecture—through service separation, clustering, load balancing, distributed caching, database replication, and effective team organization—to handle rapid user growth and maintain performance without compromising user experience.
This article explains practical techniques for designing high‑availability and scalable systems—covering entry, business, cache, and database layers—so developers can handle rapid user growth without service interruptions or degraded performance.
MariaDB 10’s multi-source replication lets a single slave pull data from multiple masters, enabling centralized querying, backup, and data consistency checks across disparate databases—ideal for OLAP, big-data aggregation, and simplifying DBA operations.