---
title: "Scalability"
slug: "scalability"
updated: 2025-06-20T17:52:20Z
published: 2025-06-20T17:52:20Z
canonical: "docs.bazefield.com/scalability"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bazefield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scalability

## Overview

The Bazefield platform is built for high scalability through its **modular design**:

- **Storage Nodes** can be added at any time to distribute data load across multiple machines.
- **Edge Buffers** are easily deployed as new plants are commissioned, further enhancing the system’s distributed design.

## Sizing

A general guideline is to limit each Storage Node to a maximum of 400,000 tags. The actual limit will depend on a variety of factors such as machine resources, number of calculated tags, EdgeBuffer data ingress rate, and tag data types.

## Example Architectures

Below are three example architectures that illustrate increasing levels of scale. Each can be deployed initially or expanded over time by adding Nodes to meet growing system demands.

### Monolithic Architecture (Small)

In this option, a **Monolithic** Master Node provides all-in-one data collection, storage, core Bazefield services, and Portal hosting.

![](https://cdn.document360.io/a0786c0f-b171-4b24-8860-c32eb7ef2738/Images/Documentation/image(159).png?sv=2026-02-06&spr=https&st=2026-11-06T19%3A51%3A26Z&se=2026-11-06T20%3A51%3A26Z&sr=c&sp=r&sig=bDtLEeDK%2F1PJ5H8UYjiWXQGsUJ5ma6HDXJy5fBTUJ0M%3D)

*Monolithic Architecture. Perfect for smaller systems.*

### Hybrid Architecture (Medium)

The **Hybrid** architecture’s size falls between the Monolithic and Decoupled designs. Like the Monolithic setup, it includes a **Master Node** hosting the Portal and core services, but adds a **Storage Node** to increase storage capacity and reduce I/O load on the Master Node. Additional Storage Nodes can be added over time as necessary.

![](https://cdn.document360.io/a0786c0f-b171-4b24-8860-c32eb7ef2738/Images/Documentation/image(163).png?sv=2026-02-06&spr=https&st=2026-11-06T19%3A51%3A26Z&se=2026-11-06T20%3A51%3A26Z&sr=c&sp=r&sig=bDtLEeDK%2F1PJ5H8UYjiWXQGsUJ5ma6HDXJy5fBTUJ0M%3D)

*Hybrid Architecture. Additional storage without a fully decoupled system.*

### Decoupled Architecture (Large)

The **Decoupled** architecture splits the **Master Node** into two roles: a **Web Server** for hosting the Portal and handling client requests, and a **Proxy Node** for managing core Bazefield services and data routing. One or more **Storage Nodes** handle I/O, long-term storage, and distributed calculations.

![](https://cdn.document360.io/a0786c0f-b171-4b24-8860-c32eb7ef2738/Images/Documentation/image(158).png?sv=2026-02-06&spr=https&st=2026-11-06T19%3A51%3A26Z&se=2026-11-06T20%3A51%3A26Z&sr=c&sp=r&sig=bDtLEeDK%2F1PJ5H8UYjiWXQGsUJ5ma6HDXJy5fBTUJ0M%3D)

*Decoupled Architecture. Fully separated components for optimal performance and resource usage.*