# Network Sizing

Network sizing is an important consideration when planning the ONEWEB architecture, as network bandwidth directly affects application responsiveness, user experience, and system stability.

The following guidelines provide **baseline recommendations** for network bandwidth planning across different tiers and environments.

***

**Bandwidth Between Platform Components**

**Network bandwidth between Web Server, Application Server, and Database Server**

Reliable and high‑speed connectivity between platform tiers is essential for stable system operation.

* **Production and Disaster Recovery Environments**
  * **Recommended minimum bandwidth:** **1 Gbps**
* **Testing Environment**
  * **Minimum bandwidth:** **100 Mbps**
  * **Recommended:** **1 Gbps**, if possible, to maintain consistency with production‑like behavior

Using higher bandwidth between tiers helps reduce latency and improves performance, especially for transaction‑heavy applications.

***

**Bandwidth Between Web Server and Client Machines**

**Intranet (LAN Network)**

For client access within a local or internal network:

* **Recommended:** **1 Gbps (Gigabit LAN)**
* **Minimum acceptable:** **100 Mbps**

Higher LAN bandwidth improves page load times and overall user experience, especially for applications with rich UI.

***

**Internet or WAN Network**

For client access over the internet or wide‑area networks:

* **Recommended baseline bandwidth:** **10 Mbps** for normal applications\
  (Applications with **no more than 50 data fields per form/page**)

If your application includes:

* More than **50 data fields per form/page**, or
* More than **3 images per form/page**, or
* Additional attachments or large payloads

You should **increase internet bandwidth proportionally** based on the additional data size.

A simple guideline is:

* **Base bandwidth:** 10 Mbps
* **Additional bandwidth:** Based on extra data fields, images, or attached files

***

**Important Considerations**

When planning network capacity, also consider:

* Peak usage periods and concurrent users
* Transaction‑heavy operations
* Integration traffic with external systems
* Media‑rich user interfaces (images, attachments, documents)
* Growth in user base and data volume over time

Under‑sized network bandwidth can become a bottleneck even when CPU, memory, and storage are adequately sized.

***

**Architectural Alignment**

Network sizing decisions should align with:

* Selected deployment architecture (Standalone, High Availability, or Cloud)
* Environment type (Testing, Production, Disaster Recovery)
* Load balancing and high‑availability strategies
* Security architecture (firewalls, DMZ, network segmentation)

Proper network planning ensures consistent performance and reliability across all ONEWEB environments.


---

# 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/installation-guide/plan-your-oneweb-installation/sizing-consideration/network-sizing.md?ask=<question>
```

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.