- examples/: c4-standard-web-app, c4-e-shop (was online-shop), c4-event-based-integration; the same models the extension offers under Archify | New Model… - model-scaffold --example <name> copies one and renames id, name, description and the overview title; never overwrites - tests cover every example and the copy; docs updated
41 lines
1.2 KiB
Plaintext
41 lines
1.2 KiB
Plaintext
schema_version: 1
|
|
elements:
|
|
ingest:
|
|
type: backend
|
|
label: Ingest API
|
|
sublabel: HTTPS in, events out
|
|
description: Accepts events from systems that cannot publish to the bus themselves.
|
|
bus:
|
|
type: messagebus
|
|
label: Event bus
|
|
sublabel: Kafka
|
|
brand: apache-kafka
|
|
description: One topic per event type; retained for seven days.
|
|
router:
|
|
type: backend
|
|
label: Event router
|
|
sublabel: validate, enrich, dispatch
|
|
description: Checks each event against its schema, adds reference data, hands it to the consumers.
|
|
diagram: 0300-components/router.archify
|
|
dlq:
|
|
type: messagebus
|
|
label: Dead-letter queue
|
|
sublabel: failed events
|
|
description: Events the router could not process; replayed by operations.
|
|
store:
|
|
type: database
|
|
label: Event store
|
|
sublabel: PostgreSQL
|
|
brand: postgresql
|
|
description: Every accepted event, for audit and replay.
|
|
notifier:
|
|
type: backend
|
|
label: Notifier
|
|
sublabel: email, chat
|
|
description: Turns selected events into messages to people.
|
|
analytics:
|
|
type: database
|
|
label: Analytics
|
|
sublabel: warehouse tables
|
|
description: Flattened events for reporting.
|