Page Comparison

...

• Notifications
  • pipeline steps
    • single implementation (for most steps)
      • usage pattern: push-pull pipeline
      • exchange type: direct
      • queues: single queue for each pipeline step, with multiple consumers per queue
    • multiple implementations (e.g., user target resolvers)
      • usage pattern: push-pull pipeline
      • exchange type: direct
      • queues: different queue for each "type" of user-target resolver, with multiple consumers per queue
  • delivery channels
    • usage pattern: pub/sub or push-pull pipeline, depending on channel implementations
    • exchange type: fanout ( ? )
• Cross-process event handling
  • usage pattern: pub/sub
  • exchange type: direct and/or topic
• Course publish event (CMS → LMS)
  • usage pattern: request-reply RPC or pub/sub
  • exchange type: default or direct

...