In any new version of SharePoint, there are changes that are bound to affect the general logic of farm design. Before the appearance of SharePoint 2016 developers are provided specific recommendations within the framework of the so-called “traditional” model, which was based on a simple three tiered approach that combines database servers, applications, and Web.
This is quite a convenient approach, and it is very easy to build a SharePoint farm. However, it has limitations of selections for each server. From the point of view of information security that meant that the vulnerable surface of each server was much more than could be.
Thanks to subsequent versions, we got a “simplified” approach, which would increase the base number of servers by selection of role, referred to distributed cache, and the internal subsystem of load balancing, ensure, if it is necessary, traffic between all servers in accordance with assignments. So the traffic of service application is always allocated by choosing an optimal unit from which it can be accessed.
In SharePoint 2016 appeared the so-called mini-roles (MinRole), which have a huge impact on the number of servers needed for farm work. Now four servers is required for a typical SharePoint 2016 environment if you use MinRole. This is very similar to other topologies, familiar in SharePoint 2013. The main difference is that only functions and features required for a specific role are switch on at the servers.
The main logic of this type of architecture can be reduced to the following advantages:
- Predefined roles
- Subsystem of load balancing application focused on the local instance
- Simplifying deployment
- High scalability of the farm
- Reducing the number of errors at setup
- Increased performance and reliability
- Projected resource planning
- Automatic settings of parameters
In general, this approach allows to improve the structure, simplify support and get a more permanent solution.