Comments on: Decision Services, Decision Agents and Event Processing http://jtonedm.com/2008/10/13/decision-services-decision-agents-and-event-processing/ James Taylor on Everything Decision Management Sun, 21 Mar 2010 19:03:55 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: Business Event Management and Decisions » JT on EDM http://jtonedm.com/2008/10/13/decision-services-decision-agents-and-event-processing/comment-page-1/#comment-11648 Business Event Management and Decisions » JT on EDM Fri, 05 Dec 2008 00:58:49 +0000 http://jtonedm.com/?p=609#comment-11648 [...] with EDA, CEP, BPM, BRMS and SOA. This is also a topic on which I blog regularly like this one on Decision Agents and this one over on my ebizQ  blog with links to a whole conversation I had with various [...] [...] with EDA, CEP, BPM, BRMS and SOA. This is also a topic on which I blog regularly like this one on Decision Agents and this one over on my ebizQ  blog with links to a whole conversation I had with various [...]

]]> By: Paul Vincent http://jtonedm.com/2008/10/13/decision-services-decision-agents-and-event-processing/comment-page-1/#comment-11369 Paul Vincent Tue, 14 Oct 2008 13:47:33 +0000 http://jtonedm.com/?p=609#comment-11369 Good post. "Don't embed business decisions in anything too tightly coupled to events or processes if you can avoid it - manage them as the corporate assets they are." Note that these are not necessarily connected notions. Some BRMSs for example let you generate COBOL, .NET and Java for the same managed rules. The same applies in Event Processing: I might want to manage rules / decisions, but deploy them as required in multiple services. Its the design-time separation (of rules and code) that is more important... Cheers Good post.
“Don’t embed business decisions in anything too tightly coupled to events or processes if you can avoid it – manage them as the corporate assets they are.”
Note that these are not necessarily connected notions. Some BRMSs for example let you generate COBOL, .NET and Java for the same managed rules. The same applies in Event Processing: I might want to manage rules / decisions, but deploy them as required in multiple services. Its the design-time separation (of rules and code) that is more important…

Cheers

]]>