Server configurations

This document outlines recommended deployment configurations for ThoughtFarmer on-premise environments. These configurations are intended to serve as starting points and may be adjusted based on organizational requirements, infrastructure standards, and scalability needs.

This guide is intended for system administrators, infrastructure teams, and technical contacts responsible for deploying and maintaining ThoughtFarmer on-premise environments. Feel free to contact ThoughtFarmer support with specific questions.

Note: In this document, the term “server” refers to a single instance of Windows Server running either on physical hardware or within a virtualized environment.

Single instance of ThoughtFarmer - Single server

Recommended for:

• Smaller environments
• Fewer than 500 users

ThoughtFarmer Licenses Required: 1.

Description: In this deployment model, the ThoughtFarmer web application and SQL database server are installed on the same server instance.

This configuration provides a simplified deployment and is typically suitable for smaller organizations or lower traffic environments.

Single instance of ThoughtFarmer - Multiple servers

Recommended for:

• Medium to large environments
• Approximately 400 to 5,000 users

ThoughtFarmer Licenses Required: 1

Description: In this configuration, the ThoughtFarmer web application and SQL Server database are hosted on separate servers.

The SQL Server environment may consist of:

• A standalone SQL Server instance
• A clustered SQL environment for improved performance and redundancy

Separating the web and database servers improves scalability and resource allocation for larger deployments.

Multiple instances of ThoughtFarmer - Multiple servers

Recommended for:

• Large environments
• Organizations requiring failover or high availability support
• Approximately 400 to 5,000 users

ThoughtFarmer Licenses Required: 2.

Description: This deployment model uses two separate web front-end servers, each hosting a ThoughtFarmer application instance.

A reverse proxy or load balancer is configured to:

• Route traffic to the primary server
• Redirect traffic to the secondary server if the primary server becomes unavailable

This configuration provides improved availability and redundancy for mission-critical environments.