Since our work in Chapter 16, The Artisan Gateway Service, only (tentatively) closed three stories, there are still several (eleven) that need to be addressed. The implementation of RabbitMQSender and the RabbitMQ message transmission strategy that was adopted also raised questions about how to propagate some of the artifacts needed for those processes—the signing key in particular—and there's also a decision pending about whether the Artisan Gateway will use one message queue for inbound traffic from artisans, or one per Artisan, and that may add another story:
-
As an Artisan, I need a message queue created and assigned to me so that I can send my data changes to the Artisan Gateway
The bulk of the stories still pending each represent a data flow process, a data transaction tied to a specific action that's undertaken...