RnD/EVOLV
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity
Page: Architecture Container Topology
Pages
Architecture Configuration Model and Tagcodering Architecture Container Topology Architecture Deployment Blueprint Architecture Deployment Controls Checklist Architecture Platform Overview Architecture Security and Access Boundaries Architecture Security and Regulatory Mapping Architecture Telemetry and Smart Storage Home
Clone
1
Architecture Container Topology
znetsixe edited this page 2026-03-23 11:54:40 +01:00
Table of Contents

EVOLV Container Topology

This page translates the deployment blueprint into a practical container/service split.

Current Repository Baseline

Today the repository contains:

  • a development stack in docker-compose.yml
  • a broad central-stack example in temp/cloud.yml

Those are useful references, but production should be split by layer.

Recommended Service Split

Edge host

edge-host-01
  - evolv-edge-nodered
  - evolv-edge-influxdb
  - optional evolv-edge-grafana
  - optional evolv-edge-broker

Site host

site-host-01
  - evolv-site-nodered
  - evolv-site-influxdb
  - evolv-site-grafana
  - optional evolv-site-broker

Central host groups

central-ingress
  - reverse proxy
  - API gateway
  - IAM

central-observability
  - central InfluxDB
  - Grafana

central-engineering
  - Gitea
  - CI/CD

central-config
  - tagcodering-backed config services

Why Split By Layer

  • better fault isolation
  • easier upgrades
  • clearer secret boundaries
  • less confusion between OT-adjacent and enterprise services

Production Guidance

  • keep development Node-RED settings separate from production settings
  • add healthchecks for every persistent service
  • back up every persistent volume
  • avoid exposing edge services publicly
  • use env files or secret injection, not inline credentials

Related Pages