Sample Topologies
The Understanding K2 Components topic described the various components that make up K2. In this section, we describe common topologies in which those components can be installed.
The topologies described are not a comprehensive or exhaustive list of all supported topologies, but rather examples of the most common topologies. Your organization may have unique or more complex requirements that may require a different topology. If this is the case, K2 recommends making use of K2's support and consulting services to assist in planning and establishing an appropriate topology for your organization's requirements.
| Topology | Description |
|---|---|
| Single Server / Standalone | The Standalone deployment scenario is best suited for low-load environments such as a development or proof of concept environment. All components are installed on the same physical server as the K2 Server. |
| Separate SQL Server | A common topology is to install the K2 databases on a dedicated SQL server, and all other application server components on another machine. |
| Distributed Environment Installation Scenario | A distributed environment consists of separate K2, IIS, and SQL servers, each server hosting different components of the K2 product, separated by server role. |
| Farm/NLB Topologies | Farm topologies typically involve multiple physical machines acting as one logical machine through a Network Load Balanced (NLB) mechanism. These topologies are ideally suited for high-load, high-availability environments. |
| SharePoint Online, 2013 and 2016 | This section describes various topology options when integrating with the SharePoint 2013-family of products. |
Due to the complex and unpredictable nature of K2 applications, it is not possible to provide specific performance metrics for various topologies.
Many organizations have multiple environments (e.g. Production, Development and Staging) used to develop and test new systems and processes. It is recommended that at least the Staging/Test environment (and ideally the Development environment as well) are configured identically to the production environment so that performance can be tested accurately and testing and troubleshooting are representative of what can be expected in the Production environment.