# Sizing Consideration When planning the installation of ONEWEB, **sizing considerations** play a critical role in selecting the appropriate architecture and determining system capacity.\ Proper sizing ensures that the platform can support expected workloads while maintaining performance, availability, and service‑level objectives. The following key questions should be addressed during the sizing and planning phase. *** ### **Environment Scope** **Which environment are you planning for?** Consider whether the sizing applies to: * **Production Environment** * **Disaster Recovery Environment** * **Testing Environment** Each environment has different requirements in terms of capacity, availability, and cost, and should be sized independently. *** ### **Application Criticality** **Is the application a critical system?** If the application must be available **24/7**, such as payment processing or mission‑critical transaction systems, a **clustered or Active‑Active architecture** should be considered to ensure continuous operation. Less critical applications with acceptable downtime may be deployed using simpler architectures. *** ### **Downtime Tolerance and SLA** **Can the system tolerate downtime for maintenance or failure? What is the SLA?** * Applications with strict uptime requirements may require **High Availability Architecture** * Applications with flexible SLAs and planned maintenance windows may use **Standalone Architecture** Downtime tolerance directly influences architecture selection and resource allocation. *** ### **Disaster Recovery Requirements** **Do you need Disaster Recovery? What are your RPO and RTO targets?** If business continuity is required, a Disaster Recovery Environment should be planned. Key considerations include: * **RPO (Recovery Point Objective)** – how much data loss is acceptable * **RTO (Recovery Time Objective)** – how quickly the system must be restored These values determine the scale and complexity of the DR environment. *** ### **Active User Volume** **How many active users will access the system?** The number of active users is a primary factor in sizing decisions. Based on user volume, you may: * Scale vertically by allocating higher CPU and memory to a Standalone deployment, or * Scale horizontally by distributing workload across multiple servers using **Active‑Active architecture with load balancing** *** ### **Transaction Volume** **How many transactions are expected per month or per year?** Transaction volume directly impacts: * Application server capacity * Database performance * Integration throughput Both average and sustained transaction rates should be considered when sizing system resources. *** ### **Peak Load Scenarios** **What is the expected transaction volume during peak times or peak events?** In addition to average load, the system must be sized to handle: * Peak business hours * Seasonal or event‑driven spikes * Short‑term bursts of high transaction volume Failure to account for peak load may lead to performance degradation or system instability. *** ### **Data Volume and Retention** **How much data will be stored, and how long will it be retained?** Data volume impacts: * Database storage requirements * Query performance * Backup and recovery strategy When planning architecture and sizing, consider both: * Number of records * Total data size over time *** ### Architectural Outcome By answering these questions, you will be able to: * Select the appropriate ONEWEB architecture (Standalone, HA, or Cloud) * Estimate server capacity and scaling requirements * Align infrastructure design with business and SLA expectations These sizing considerations form the foundation for detailed architecture design and installation planning. --- # 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.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.