Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Would something like ZeroMQ work to subscribe/publish these messages? Commented Sep 14, 2016 at 16:00
  • @Joe Theoretically yes, however it is a very lightweight client and doesn't support things like transactional processing (Rollback, Retries, Backouts, etc...) and persistent queues (avoiding downtime message loss). This question really comes down to, "How serious is the situation if I were to lose a message or fail to process it?" If the answer is "Not much" or you have some margin of error then ZeroMQ is appropriate. Commented Sep 14, 2016 at 16:10
  • Ah, I see you were linking ActiveMQ, I missed that - I see how that could be more appropriate. Thanks! Commented Sep 15, 2016 at 8:31
  • @Joe No problem. Architecture is a discipline of itself. The most important takeaway I stress to people is to determine non-functional requirements from your quality attributes. Where some requirements are quantitative and concrete, others are qualitative and subjective. The most important part of my job when writing architecture documentation is defining Rationale. It is hard to convince the business and stakeholders of an approach without it. You might want to consider documenting this. Commented Sep 15, 2016 at 12:36