Before taking a serious look at the transmission-mechanism options, it would be beneficial to have a solid definition of what, exactly, constitutes a message being transmitted. At a minimum, given what the data flows coming into the Artisan Gateway service look like, and with some idea of what the actual data for a typical data object being transmitted entails, it's apparent that a message needs to be able to handle structured data. Internally, that's probably best represented by a dict, if only because they are easy to serialize and un-serialize into at least two different formats that are easily transmissible: JSON and YAML. We've already established data dictionary structures for the objects whose state data can be stored. A Product, for example, from an Artisan's perspective, whose data dictionary has been rendered into JSON looks like this:
{...
