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…
Part 1 said I do not predict a sticker. Part 2 built the demand curve. This post is the commercial layer: how I turn that curve into a scored grid without burying policy inside LightGBM leaves….
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…
Part 1 of this series argued that a shelf-price system should not spit out “the right sticker.” It should score a grid with a demand curve underneath. This post is the curve: how I build a…
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…
Most “pricing ML” demos train a model that spits out a dollar figure and call it done. That works in a notebook. It fails the first week a category manager asks why milk moved 12 cents…
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…