Doing it right
The platform gives you publish, select, deliver. Five habits make it age well. Know them by name.
Normalize onto the bus
The bus carries one canonical shape per business concept. Convert to it on the way in, convert from it on the way out. The test: if adding a second destination means editing a pipeline, delivery logic is in the wrong place.
Map at the edges
Transformations happen in exactly two spots: the receive pipeline (source to canonical) and the send pipeline (canonical to destination). Nothing in the middle reshapes messages.
Validate at the edge
Check structure and the fields that matter in the receive pipeline. Bad messages get rejected loudly, so everything on the bus is clean and every subscriber can trust it.
Fail loud, never drop
A message that matches nothing, runs out of retries, or turns out poison goes to Suspended status (the dead-letter channel, in more technical terms): persisted, visible in tracking, ready to resume or terminate. Never silently discarded. Loud failure is recoverable. Silent failure is not.
Design for replay
Ask of any flow: if the destination was down for an hour, how do I reprocess that hour? The answer should be "replay from the bus," never "re-extract from the source by hand."
The common thread
All five are one idea: the bus is the system of record for messages in motion. Keep it canonical and clean, and every failure becomes a replay instead of an incident.
Snapshots: configuration that travels
When you need to archive a setup, share it, or move it between environments, take a snapshot: the complete configuration of an Application, or of the entire environment, as one portable JSON file. Ports, pipelines, message types, schemas, maps, variables, constants, routing. How the system is set up, never what it has been doing: transactions, runtime state, and tracking history are never included, so sensitive message data stays out of your configuration files by design.
Two things are sensitive, so they are opt-in: Authentications (credentials) and Constants values. Include either and the snapshot seals them under a single password, like a password-protected PDF. Everything else stays plain, diffable JSON.
Almost there
Publish-select-deliver, the building blocks, the adapters, the habits. One short module to go: the AI assistant, what it helps you build, what it costs, and why your data never leaves your tenant.
Check yourself
Three quick questions on this module, in the same style as the exam. Not graded, not recorded, just practice with instant explanations.