About This Architecture

C4 container diagram modeling a data processing system with n8n workflow automation orchestrating ingestion from batch sources and config services. Data flows through a message broker queue into an orchestrator service that enriches and transforms records, persisting results to PostgreSQL and indexing in Elasticsearch for analytics. This architecture decouples ingestion from processing, enabling scalable, asynchronous data pipelines with clear separation of concerns. Fork this diagram on Diagrams.so to customize OCI services, add monitoring layers, or adapt the workflow for your data stack. The pattern supports high-throughput batch and streaming workloads while maintaining transactional consistency.

People also ask

How do you design a scalable data processing pipeline with n8n and message brokers on OCI?

This C4 container diagram shows a decoupled architecture where n8n ingests data from batch sources and config services, publishes to a message broker queue, and an orchestrator service consumes messages to transform and persist data to PostgreSQL while indexing in Elasticsearch. This pattern enables asynchronous, fault-tolerant ETL with clear separation between ingestion, processing, and storage l