# Container Structure

In a cloud environment, **ONEWEB** can be deployed using a **container‑based architecture**.\
This approach allows platform components to run as isolated containers, improving scalability, portability, and operational consistency.

ONEWEB supports both:

* **Distributed container deployment** using a standard Docker engine, and
* **Orchestrated container deployment** using **Kubernetes** for production‑grade environments.

***

### Containerized Deployment Overview

In a containerized installation, ONEWEB platform components are packaged and deployed as individual containers, each responsible for a specific platform capability.

This model enables:

* Clear separation of responsibilities
* Independent scaling of platform services
* Improved fault isolation
* Consistent deployment across environments

***

### ONEWEB Platform Containers

A standard ONEWEB containerized deployment includes the following containers:

* **oneweb-iam2**\
  Provides 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 system 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 generating deployable page artifacts.
* **oneweb-designersuite**\
  Provides AppSpace, App Designer, Process Designer, and other supporting utilities.
* **Apache container**\
  Acts as the web server handling HTTP requests and serving static content.
* **Database container**\
  Provides persistent data storage for platform configuration and application data.

Each container focuses on a well‑defined responsibility, allowing the platform to remain modular and easier to manage at scale.

***

### Kubernetes Reference Architecture

For orchestrated environments, ONEWEB commonly uses **Kubernetes** to manage container lifecycle, scaling, and resilience.

In a Kubernetes‑based deployment:

* Containers are managed as distributed workloads
* Platform services can scale horizontally
* Health checks and restart policies improve stability
* Traffic between services is managed through orchestration mechanisms

The following diagram illustrates a **sample Kubernetes architecture** used for deploying 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>

***

### How Container Structure Fits into Cloud Architecture

Within the overall ONEWEB architecture:

* **Cloud Architecture** defines *where* the platform is hosted
* **Container Structure** defines *how* platform components are packaged and executed
* **Runtimes** operate inside containers to execute application logic
* **Designer services** run as managed platform components

This layered approach ensures that ONEWEB can operate consistently across cloud providers while supporting scalability and resilience.


---

# 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/getting-started/installation-guide/plan-your-oneweb-installation/design-oneweb-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.