Configurator · Architecture v3

pendingrepo acme/acme-ccccommit 7c8a91dbranch mainby markus.bauer@acme.example· 2026-05-13 09:18

Confluencespace CCCConfiguratorAuto-doc draftpreview · not published

Configurator · Architecture v3

Drafted by Bridge · commit 7c8a91d by markus.bauer@acme.example · 3 mermaid diagrams will render as PNG attachments on publish

Configurator · Architecture v3

This page documents the current Configurator architecture as of 2026-05-13. It is auto-generated from the main branch of acme-ccc and refreshed on every push to mapped paths.

1 · System overview

The Configurator is an Edge-SSR Next.js app fronting a set of Java microservices. Inventory pricing and stock data flow in via the Inventory API; user choices and orders flow out via the order pipeline.

2 · Bounded contexts

Configurator UI — Edge SSR, 3-step flow, multi-locale
Inventory API — Sub-200ms pricing fan-out
Order pipeline — Async, eventual consistency with dealer inventory
Compliance broker — R155 evidence collector

3 · Sequence: build → save

Diagram below is auto-rendered from docs/architecture/build-save.mermaid.

[mermaid sequence diagram · 6 lifelines · 14 messages]

4 · Caching strategy

Two layers: CDN at the edge (immutable assets, 7d), and a write-through cache in the Inventory API (1m TTL for prices, invalidated on inventory mutation).

Source commit

Repoacme/acme-ccc

Branchmain

SHA7c8a91d

Authormarkus.bauer@acme.example

Messagefeat(api): Inventory API integration + cache strategy

Diff summary

Updated API contract diagrams (replaced 2 PlantUMLs with mermaid)
Added Inventory API integration sequence
Clarified caching strategy (CDN + edge)
Removed deprecated v1 endpoints reference

Triggered by mappings

src/configurator/**src/api/****/*.openapi.yaml

Edit mappings →

Magic-link approve

Same actions are wired into the notification email — reviewers can approve/revise/reject without logging in. Tokens are HMAC-SHA256 signed.