Composing Order Messages From Service Data in Transmitly

This article continues a series on building a message pipeline where an order is created and a buyer is notified. The Ordering service dispatches an OrderCreated intent, and the Communications service then assembles the final content. The first pipeline produced only a minimal confirmation email, which proved the flow but offered little value to customers. The author now focuses on enriching the message with recipient details and order information, with Ordering supplying the facts it owns. The Ordering service projects its order aggregate into a communication model containing order identifiers, date, items, and total. The article distinguishes this transactional model from the content model that evolves during composition and rendering.