# Network Requirements A reliable network infrastructure is a fundamental prerequisite for running **ONEWEB**.\ All platform components communicate over a **TCP/IP network**, making network readiness essential for system stability, performance, and scalability. This section outlines the baseline network requirements for ONEWEB deployments. *** ### TCP/IP Network Connectivity ONEWEB requires a physical or virtual **TCP/IP network** to enable communication between platform components. The following components must be able to communicate over the network: * Client machines (end users and designers) * Web servers * Application servers * Database servers * Load balancers (if applicable) Each server running ONEWEB components must have: * At least **one network interface** * Stable network connectivity to other platform components This requirement applies to on‑premises, cloud, and container‑based deployments. *** ### Load Balancing Requirements **Load balancing** is required when ONEWEB is deployed in a clustered or distributed configuration. Load balancing is typically used when: * Two or more **Web Servers** are deployed * Two or more **Application Servers** are deployed * High Availability or Cloud Architecture is implemented Both **hardware‑based** and **software‑based** load balancers are supported. *** ### Role of Load Balancing in ONEWEB From an architectural perspective, load balancing helps to: * Distribute incoming client requests evenly * Prevent individual servers from becoming bottlenecks * Improve system availability and fault tolerance * Support horizontal scaling of platform components Load balancers are commonly positioned in front of the Web Tier and, in some architectures, the Application Tier. *** ### Network Architecture Considerations When designing network infrastructure for ONEWEB, consider: * Network latency between tiers (Web, Application, Database) * Bandwidth requirements based on user concurrency and transaction volume * Firewall and security zone boundaries (Internet, DMZ, Internal Network) * Integration with High Availability and Cloud Architecture designs Network design should align with overall **Platform Architecture** and **Security Requirements** to ensure predictable behavior across environments. *** ### Summary of Network Requirements Before proceeding, ensure that: * A TCP/IP network is available and stable * All ONEWEB components can communicate over the network * Load balancing is planned for clustered or HA deployments * Network design aligns with security and deployment architecture These requirements establish the network foundation needed to run ONEWEB reliably. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.onewebstack.com/oneweb-platform-th/getting-started/prerequisites-and-system-requirements/network-requirements.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.