1

Architecture Deployment Blueprint

znetsixe edited this page 2026-03-23 11:54:40 +01:00

Table of Contents

• EVOLV Deployment Blueprint
• Layered Deployment Model
• Edge
• Site
• Central
• Target Topology
• Compose Strategy
• Environment Strategy
• Rollout Order
• Related Pages

EVOLV Deployment Blueprint

This page turns the architecture into a concrete deployment model.

Layered Deployment Model

Edge

Purpose:

• PLC and field connectivity
• local Node-RED execution
• local InfluxDB for resilience and digital-twin use

Recommended services:

• Node-RED
• InfluxDB
• optional local Grafana
• optional local broker

Site

Purpose:

• plant-local aggregation
• mediation between edge and central
• local dashboards and diagnostics

Recommended services:

• Site Node-RED / CoreSync
• Site InfluxDB
• Site Grafana
• optional broker

Central

Purpose:

• API ingress
• IAM and governance
• fleet analytics and dashboards
• source control, CI/CD, and configuration services

Recommended services:

• reverse proxy / ingress
• API gateway
• IAM
• central InfluxDB
• central Grafana
• Gitea
• CI/CD
• tagcodering-backed configuration services

Target Topology

flowchart LR
    subgraph EDGE["Edge Host"]
        ENR["Node-RED"]
        EDB["InfluxDB"]
        EGR["Optional Grafana"]
    end

    subgraph SITE["Site Host"]
        SNR["Site Node-RED / CoreSync"]
        SDB["Site InfluxDB"]
        SGR["Site Grafana"]
    end

    subgraph CENTRAL["Central Platform"]
        RP["Reverse Proxy / Ingress"]
        API["API Gateway"]
        IAM["IAM"]
        CDB["Central InfluxDB"]
        CGR["Grafana"]
        GIT["Gitea"]
        CICD["CI/CD"]
        CFG["Tagcodering Services"]
    end

    ENR --> EDB
    ENR <--> SNR
    EDB <--> SDB
    SNR --> SGR
    SNR <--> API
    RP --> API
    API --> IAM
    API <--> CFG
    SDB <--> CDB
    CDB --> CGR
    GIT --> CICD

Compose Strategy

Do not use one flat compose file for all layers in production.

Preferred split:

• compose.edge.yml
• compose.site.yml
• compose.central.yml

This gives clearer ownership, easier secret separation, and safer updates.

Environment Strategy

• tracked compose files contain variables only
• real values live in server-local .env files or a secret store
• env files should be separated by layer and environment

Rollout Order

1. edge baseline
2. site mediation
3. central platform
4. tagcodering integration
5. smart telemetry policy

Related Pages

• Deployment Controls Checklist
• Platform Overview
• Configuration Model and Tagcodering