Platform engineering integrations and automations

What this work has in common

These guides describe shapes more than named business processes, and they sit underneath the rest of the library. A facade, a change capture pipeline, a webhook fan-out and a migration off a batch file are each something several teams were about to build separately, in slightly different ways.

They are also where the expensive mistakes are made. A decision about retries, idempotency or identity at this layer is inherited by every workflow built on top of it. A facade that loses the caller’s identity means every downstream audit log shows a service account. A fan-out without replay means a consumer that was down for an hour has a gap nobody can fill.

The systems vary more here than in the other categories: a Postgres or Snowflake database, an SFTP server, Datadog for monitoring, Stripe or Zendesk as webhook sources, and whichever CRM and ERP the consumers need. What stays the same is the set of guarantees: one contract per consumer, ordering and deletes preserved, delivery that can be retried and replayed, and a cutover you can prove is safe.

The four guides cover the API facade, change data capture, webhook fan-out and the migration from SFTP batch files to APIs. They pair with the data operations guides, which build on the same capture and delivery patterns.

Each one is written so the pattern can be built once and reused, with the first consumer as the worked example.