# Container Structure

### Overview

In a cloud environment, **ONEWEB** can be deployed using a **containerized architecture**. This deployment model allows platform components to run as isolated containers, improving scalability, portability, and operational consistency.

ONEWEB supports both:

* **Standalone container deployments** using a standard Docker engine, and
* **Orchestrated container deployments** using Kubernetes for larger‑scale and highly available environments.

This flexibility allows organizations to choose an appropriate container strategy based on their operational maturity and infrastructure requirements.

***

#### Containerized Deployment Model

In a containerized setup, ONEWEB platform components are packaged and deployed as individual containers, each responsible for a specific function within the platform.

This approach provides:

* Clear separation of responsibilities
* Independent scaling of platform components
* Improved resilience and fault isolation
* Easier deployment across environments

***

#### ONEWEB Container Components

A typical ONEWEB containerized installation includes the following containers:

* **oneweb-iam2**\
  Authentication and authorization services.
* **oneweb-uxp**\
  User Experience Runtime responsible for executing user‑facing applications.
* **oneweb-bpp**\
  Business Process Runtime for executing workflows and process logic.
* **oneweb-mfr**\
  Microflow Runtime for backend services and integration logic.
* **oneweb-mfd**\
  Microflow Designer for designing microservices and integration flows.
* **oneweb-pgd**\
  Page Designer for designing web and mobile application pages.
* **oneweb-pgb**\
  Page Builder for building deployable page artifacts.
* **oneweb-designersuite**\
  A consolidated container that includes AppSpace, App Designer, Process Designer, and supporting utilities.
* **Apache container**\
  Web server responsible for handling HTTP requests and serving static content.
* **Database container**\
  Persistent data storage for application and platform data.

Each container focuses on a specific responsibility, enabling modular deployment and easier management.

***

#### Kubernetes‑Based Architecture

For production and large‑scale environments, ONEWEB is commonly deployed using **Kubernetes** as a container orchestration platform.

In a Kubernetes deployment:

* Containers are grouped into pods and managed as services
* Platform components can scale horizontally based on workload
* Health checks and restart policies improve system resilience
* Traffic is routed efficiently between platform services

The following diagram illustrates a sample Kubernetes‑based architecture for ONEWEB:

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F5tbYLxPTki9zrpnbh9jh%2FArchitecture.png?alt=media&#x26;token=f2015984-875d-4a93-9dce-700e3dedd778" alt=""><figcaption></figcaption></figure>


---

# 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/overview/platform-architecture/cloud-architecture/container-structure.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.