tag:blogger.com,1999:blog-8825992.post8225971593034234909..comments2019-02-13T20:54:50.768-08:00Comments on Electric Duncan: A Sinfonia on Messaging with txAMQP, Part IUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8825992.post-62921260498572466842009-06-16T22:35:24.357-07:002009-06-16T22:35:24.357-07:00Hey glyph, thanks for your comment.
In answer to ...Hey glyph, thanks for your comment.<br /><br />In answer to your questions, in part, I refer you back to the post:<br /><br />"This example is not meant to fully justify messaging for businesses, but rather to provide a simple use case for which we can write some simple (and less than robust) code. It is a toy, but a conceptually useful one with a solid, concrete foundation."<br /><br />For a more complete response, I would ask readers to consider the following:<br /><br />The problem in illustrating messaging examples is that the need for it has arisen organically over the past decade or so within complex environments with many duplicated resources, redundant solutions, multiplied maintenance burdens, divergent data, etc. Large, diverse systems that are expensive to maintain and whose components have intersecting needs are the ones that benefit most from messaging.<br /><br />As such, a simple example will necessarily be artificial. However, if one can accept the possibility of the need for messaging, and then work through a simple case (however contrived), then by extrapolation, they can apply this new understanding and first-hand knowledge to real-life situations in complex environments with which they are familiar. <br /><br />Couple this initial exposure with the related reading materials, and a motivated, interested reader has everything they need to assess their own large environments and begin envisioning the ways in which messaging -- in the long run -- can save them time, effort, and money.<br /><br />Sadly, this post suffers from more than common marketing problems: it's awkward at best and doesn't pull the story together concisely. I have every intent of returning to it after the next few posts finish up this series to see what I can do to reshape it. That may or may not happen, time will tell.Duncan McGreggorhttps://www.blogger.com/profile/17155270977759488515noreply@blogger.comtag:blogger.com,1999:blog-8825992.post-38770648257911696982009-06-14T18:19:01.181-07:002009-06-14T18:19:01.181-07:00This is an interesting series; dynamic updates are...This is an interesting series; dynamic updates are a subject near and dear to my heart. Unfortunately it suffers from a common problem of marketing literature for ESBs: an incomplete description of the problem.<br /><br />There are two questions that I feel need to be answered to justify your conclusion:<br /><br />Where are the inefficiencies in the business that FĂona is complaining about? Copying and updating from export files might be perfectly fine. You hint at the problem when referring to the shipping guy's "unneeded trips down the glen", but you don't say why he's making those trips.<br /><br />Also, what is the advantage of this decentralized system over the simpler solution of all parties using a single, centrally maintained, web-based business software?<br /><br />As it happens, if I fill in the gaps myself, I believe your conclusions. I just think this could be a very persuasive example with some more explication.glyphhttps://www.blogger.com/profile/07021175796928101086noreply@blogger.com