Low Level Network Diagram Example for CI/CD Pipeline Stages

Tech architecture infographic titled "CI/CD Pipeline Stages" using archetype PROTOCOL HANDSHAKE (numbered exchanges). Show a left-to-right numbered exchange diagram that explains how a CI/CD pipeline works at a low level for a mid-level developer, while still fitting a clean handshake-style sequence. Render labeled boxes connected by directional arrows: Developer Workstation, Git Repository, CI Orchestrator, Build Runner, Artifact Registry, Test Runner, Approval Gate, CD Deployer, Target Environment, Monitoring Service, plus supporting generic boxes Browser, API, DB, Cache, Queue as platform components where relevant. Each box must include a simple icon, a canonical English name, and a one-line English role description. Example box roles: Developer Workstation — 'Creates commit and pushes code'; Git Repository — 'Stores source and triggers webhook'; CI Orchestrator — 'Schedules pipeline jobs'; Build Runner — 'Compiles code and builds artifact'; Artifact Registry — 'Stores versioned build outputs'; Test Runner — 'Executes unit and integration tests'; Approval Gate — 'Checks manual or policy approval'; CD Deployer — 'Applies release to target'; Target Environment — 'Runs deployed application'; Monitoring Service — 'Collects logs and health signals'; Browser — 'User interface for pipeline status'; API — 'Pipeline control and webhook endpoint'; DB — 'Stores pipeline metadata and run history'; Cache — 'Speeds dependency reuse'; Queue — 'Buffers asynchronous jobs'. Use arrows with short English labels that are technically accurate: 'git push over HTTPS/SSH', 'webhook event JSON', 'enqueue job', 'clone repository', 'restore dependency cache', 'build artifact', 'push image/artifact', 'test results XML/JSON', 'approval decision', 'deploy manifest', 'health check HTTPS', 'status callback', 'store run metadata', 'read cached layers'. Make the central flow a numbered handshake sequence with 7 clear exchanges: 1) Developer Workstation -> Git Repository: commit push over HTTPS/SSH. 2) Git Repository -> API: webhook POST with commit metadata. 3) API -> Queue: enqueue pipeline job; Queue -> CI Orchestrator: job dispatch. 4) CI Orchestrator -> Build Runner: start build; Build Runner -> Cache and Git Repository: fetch source and dependencies; Build Runner -> Artifact Registry: publish artifact. 5) CI Orchestrator -> Test Runner: run tests against artifact; Test Runner -> DB/API: upload test results and status. 6) API/Approval Gate -> CD Deployer: approved release instruction; CD Deployer -> Target Environment: deploy package or container and run migration if needed. 7) Target Environment -> Monitoring Service/API/Browser: health check 200 OK, logs, metrics, deployment status visible to user. Include proper protocol labels where appropriate: HTTPS, SSH, REST, webhook POST, JSON, TCP. Keep Browser/API/DB/Cache/Queue visibly integrated as generic platform services, not as cloud-vendor products. Add a numbered legend 1-7 in English walking through the lifecycle with concise explanations matching the arrows and components. Include subtle notes that this is a conceptual developer-blog diagram, not an audited reference architecture. Visual style: minimal flat, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a developer pink & teal palette with soft neutrals, high contrast labels, clean grid, generous spacing, crisp arrows, modern flat icons, calm technical mood, minimal decorative background, generic cloud icons only where needed. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).