Repository Layers — cómo el monorepo agrupa servicios por concern (capa), no por entorno. ↓ service-map · overview · ⬆ intro de la sección

Repository Layers

This monorepo groups services by concern (layer), not by deployment environment.

Layers

• data-layer/: shared databases and state stores (PostgreSQL, Redis, InfluxDB, Qdrant)
• infrastructure/: foundational runtime services (Kafka, Mosquitto, n8n, Portainer, Chat Server, etc.)
• ingestion/: data ingestion/normalization pipelines (Telegraf and bridges)
• processing/: stream/batch processing (microservices, Airflow)
• platform/: end-user and business applications (Portal, Chat UI, ThingsBoard, Chatwoot)
• security/: identity and security services (Zitadel)
• deployment/: Ansible/scripts for host bootstrap, core/system/apps deploy, and shared automation
• visualization/: dashboards and documentation site (Grafana, Docusaurus)

Ownership rule

• Cross-cutting knowledge (architecture, operations, technologies) lives under docs/internal/.
• Each service keeps a minimal README.md as a gateway and links to the canonical docs page under docs/internal/services/....