| title | Topologies for Web Synchronization | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine | ||
| ms.reviewer | |||
| ms.technology | replication | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
||
| ms.assetid | 59444faf-bcb6-4421-a3df-8715753e453b | ||
| author | MashaMSFT | ||
| ms.author | mathoma |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] You can choose from a variety of [!INCLUDEmsCoName] [!INCLUDEssNoVersion] Web synchronization replication topologies. Common ways to configure Web synchronization include:
-
Single server
-
Two servers
-
Multiple [!INCLUDEmsCoName] Internet Information Services (IIS) systems and [!INCLUDEssNoVersion] republishing
For information about configuring Web synchronization, see Configure Web Synchronization.
In the simplest topology, IIS, the [!INCLUDEssNoVersion] Publisher, and the [!INCLUDEssNoVersion] Distributor all reside on a single server. Subscribers synchronize by connecting to IIS on the Publisher. The Publisher can be located behind a firewall.
Note
This configuration is recommended only for intranet scenarios. For other scenarios, it is recommended that the IIS server and [!INCLUDEssNoVersion] Publisher/Distributor be on separate computers.
You can place IIS on one server and configure the [!INCLUDEssNoVersion] Publisher and Distributor on another server. The server running IIS can be isolated from the Internet by a firewall. Subscribers synchronize by connecting to IIS.
If you need to support very large numbers of Subscribers that synchronize at the same time, you can partition the work across multiple computers running IIS.
If further load balancing is required on the computer running [!INCLUDEssNoVersion], you can create a republishing hierarchy on multiple computers. The top-level Publisher publishes data to Subscribers, which in turn republish the data, load balancing requests from the Subscribers.
Note
Subscribers can only synchronize with a specific Publisher. For example, a Subscriber to republisher A cannot synchronize with republisher B when A is not available.
Configure Web Synchronization
Web Synchronization for Merge Replication