# Standalone Architecture

**Standalone Architecture** is a simple, easy‑to‑maintain, and cost‑effective deployment model for the ONEWEB Platform.\
This architecture is suitable for **less critical systems** where a certain amount of downtime for system recovery or upgrades is acceptable.

In this model, ONEWEB is deployed using a standard **three‑tier architecture**, which consists of:

* **Web Tier**
* **Application Tier**
* **Database Tier**

This architecture provides a clear separation of responsibilities while keeping deployment and maintenance straightforward.

***

### Architecture Structure

The Standalone Architecture is based on the following three tiers:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fl8uHvdgWAZER2Stpyhye%2F0?alt=media" alt=""><figcaption></figcaption></figure>

* **Web Tier**\
  The Web Tier is responsible for receiving requests from clients or a load balancer.\
  It processes static content requests and forwards business logic requests to the Application Server in the Application Tier.
* **Application Tier**\
  The Application Tier processes requests from clients using application server middleware.\
  This tier handles business logic execution and coordination between platform components.
* **Database Tier**\
  The Database Tier is responsible for persisting data into storage, including platform configuration data and application data.

***

### Deployment Options and Flexibility

In the reference diagram, the Standalone Architecture is shown with **three separate server instances**, one for each tier.\
This represents the **recommended architectural separation** for clarity, security, and performance.

However, ONEWEB allows flexibility in how these components are deployed:

* Each tier (**Web**, **Application**, and **Database**) can be deployed on **separate servers**
* Firewall or network infrastructure can be placed between tiers to enhance system security and performance
* Alternatively, all components can run on the **same server**, provided that the server has sufficient capacity to support all tiers
* A mixed approach is also possible, such as:
  * One server for the **Web Tier**
  * A second server for the **Application Tier and Database Tier**

The final deployment decision depends on:

* Available hardware resources
* Security requirements
* Network policies
* Performance expectations

***

### When to Use Standalone Architecture

Standalone Architecture is a suitable choice when:

* System simplicity and lower cost are priorities
* The application can tolerate planned downtime
* The workload and usage are predictable
* The environment is used for development, testing, or small‑scale production systems

For systems that require higher availability, fault tolerance, or elastic scaling, alternative deployment models such as **High Availability Architecture** or **Cloud Architecture** should be considered.


---

# 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/design-oneweb-architecture/standalone-architecture.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.