A copilot “fixed” a stuck order by calling create-order again. The chat said the first call timed out. The warehouse already had the order. The second call created a twin. Nobody had sent an Idempotency-Key. The…
A new partner should not mean a new Function App repo. I treat enterprise integration patterns as a catalog of connectors and a YAML list that names them. The C# already lives under functions/. The partner…
Partners still drop files into named folders. Downstream still wants decompress, transform, compress, or encrypt. I do not encode that as a C# if/else chain per partner. I treat azure service bus routing as a YAML…
Partners still drop CSVs. Downstream still wants JSON records, paged REST, or a webhook that never skips a batch. I do not hide that work in one mega Function. I keep azure integration architecture as three…
Partners still send OpenPGP files. Downstream still wants JSON, zips, and an SFTP drop. I do not hide that work inside one “crypto Function.” I keep pgp encryption azure at two pipeline edges: preprocessing decrypts inbound…
Partners still drop files on SFTP. Azure still wants blobs, queues, and a ledger you can audit. SFTP integration on this stack is not “one Function that does everything.” It is three small, config-driven connectors: publish…
The first time a partner changes a request field from orderId to externalOrderId, you learn whether you have an edge or a tangle. If five projects each map that field in their own controllers, you get…
Most integration estates do not fail because someone picked the wrong queue product. They fail because every project rebuilds the same verbs—file drop, route, transform, deliver—with slightly different code, different secrets handling, and no shared ops…