The SharePoint 2013 farm topology is used in a production environment with two-tier and three-tier topologies, see MSDN
http://technet.microsoft.com/zh-cn/library/ee805948 (v=office.15). aspx
Three-layer topology map
You can add a Web server to the Web tier. These servers can be configured as traditional WEB servers to handle user requests, or they can be configured to host private query components or other service components.
You can add farm servers to the application tier and configure them as dedicated servers to host the SharePoint Central Administration site, or to host other services (such as crawl components, query components, and profile pages) that require dedicated resources or are isolated from the Web tier in the server farm.
You can add a database server to the database tier to implement stand-alone instances, database mirroring, or failover clustering. If you want to configure a server farm for high availability, database mirroring or failover clustering is required at the database level.
Two-layer topological diagram
The two-tier topology is a medium-sized architecture (for businesses below 10000 people). The advantage of this is that it separates the DB from the Web, which means that the Web role and application are on the same server and the DB is on the other server, which belongs to the midsize farm.
After a brief look at the topology of SharePoint 2013 (detailed topology is attached to the post), the following is the focus of this article, a frequently overlooked issue, the SharePoint security Policy (do you still have a DOMAIN\Administrator account to use everywhere?) )。
Medium-level security policy
A medium-level security policy is one of the best practices for installing SharePoint. By giving each account a lower privilege, you can effectively limit the damage to the system after the hacker gets the account. Also comply with the install SharePoint 2013 minimum permissions (least-privilege) contract. Detailed details are detailed below
SQL Server Installation