Topic Last Modified: 2010-12-08
If your organization requires support for fewer than 5,000 Access Edge service client connections, 1,000 active Lync Server Web Conferencing service client connections, and 500 concurrent A/V Edge sessions, and high availability of the Edge Server is not important, this topology offers the advantages of lower hardware cost and simpler deployment. If you need greater capacity or you require high availability, you need to deploy the scaled consolidated Edge Server topology. For details, see Reference Architecture 2: Scaled Consolidated Edge (DNS Load Balanced).
For simplicity, the following figure does not show any Directors deployed but in a real world production deployment they are recommended. For details about the topology for Directors, see Components and Topologies for Director. The reverse proxy is also not load balanced but if it was, it would require a hardware load balancer. Domain Name System (DNS) load balancing is not an option for load balancing reverse proxy traffic.
|For clarity, the .com DNS zone represents the external interface for both reverse proxy and consolidated edge servers, and the .net DNS zone refers to the internal interfaces. Depending on how your DNS is configured, both interfaces could be in the same zone (for example, in a split-brain DNS configuration).|