Skip to content

Instantly share code, notes, and snippets.

@jgpawletko

jgpawletko/mb-noodles.md

Last active August 29, 2015 14:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jgpawletko/ba77731a1ad1e4d0d175 to your computer and use it in GitHub Desktop.
Save jgpawletko/ba77731a1ad1e4d0d175 to your computer and use it in GitHub Desktop.
Download ZIP
message routing key component noodling
Raw
mb-noodles.md 
2015-02-08:

Topic Exchange Routing Key Proposal

PROPOSED TEMPLATE:	<app>.<service>.<message type>.<producer reference id>

bag validation:	 rstar.xip_validate.req.b78bc9bf-77a1-4d16-95ef-23d1d75b060f
video transcoding:	 rstar.video_xcode.req.3b7d3a3f-f4ea-408c-aedc-ba2e06471da4
file identification: rstar.file_identify.res.c9aebc65-e90b-43fc-b776-e52399e77223


Older proposal follows:

message broker routing-key noodling

  • investigating AMQP as a central component in a distributed system
    • this is all a work in progress, but I wanted to capture my current thinking
    • need to map against use cases to refine...

<application id>.<service id>.<message type? e.g., request, response, error, info, warn, debug>[.<job id>][.<object id>]

max routing key length = 255 chars

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment