A Sinfonia on Messaging with txAMQP, Part V

A Sinfonia on Messaging:

1. The Voice of Business
   
2. The Voice of Architecture
3. RabbitMQ and txAMQP
   
4. The Voice of Code
5. The Voice of Code, continued

In the last post, we started to get into some Twisted AMQP code, converting our architecture into implementation. We conclude those efforts here with order validation, billing, and status in MacGrudder's kilt store.


Validation and Billing

pass it onto the next step in our business process: order validation and billing

[valid orders]

[invalid orders]

[push to internal tracking and communicate with other services]


Status

Now that we've got a message indicating that a kilt is approved for manufacture, the meat of the business happens: creating the kilt. The core component here is MacGrudder, his tailoring skills, and the push of a button on an internal app when he completes the order. That button push starts the last leg of an order's journey though our messaging system.

[publish subscribe]

[message translators for various endpoints]


Recap

What we've done in the examples above is taken some basic use cases in a messaging scenario and then explored possible implementations using some basic patterns in enterprise messaging.


References

• Enterprise Integration Patterns, Chapter 1

• The AMQP Spec
• The async Python library for AMQP