February 10, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
James Taylor
James Taylor's Decision Management
James is one the leading experts in enterprise decision management, a published author and a principal of Smart (enough) Systems LLC. His blog discusses the use of decision management technologies like predictive analytics and business rules to deliver agility, improve business processes and bring intelligent automation to SOA.

« Decision Service Design | Main | Some thoughts on the fallacies of business process execution »

November 29, 2007
More thoughts on decision services

After my post on decision service design, Beth replied with a thoughtful post of her own. Beth raises the question of how many types of decision service there might be. I agree that there are several but there are many patterns within each type for specific decision making scenarios.

  • Short-running, stateless, synchronous decision services are one type.
  • The longer-running, wait for a human to intervene sometimes kind of decision service Beth identifies is interesting. I am not sure I would model this as a single decision service as it might make more sense to handle the long running pieces with a process while keeping the decision service very focused on trying to make the automated decision. Such a process, where a decision service attempts to take a decision and puts something on someone's worklist when it cannot is, indeed, a classic decision service / process pattern.
  • Some models of decision services do not have the decision service requesting more information. Instead they expect the decision service to fail to make a decision and to reply to that effect while identifying the information it lacked. Another service would then fetch that information and call the decision service again. While this makes decision services highly reusable and very portable as well as simple to implement, it can also be a limiting factor to their usefulness.
  • When talking to folks working in the event processing space, like my friend Paul who blogs over on the Tibco CEP blog, the management of state in decisions is critical to the event processing approach. Perhaps then there is another kind of decision service, one that is stateful and handling decisions that relate to event processing rather than process execution.
  • Moving on to asynchronous execution one gets into classic publish/subscribe processing where a decision service might subscribe to an event, execute in response and then decide what events to publish as a result.

I am sure there are others. I have started a wiki entry for Decision Service to which you should all feel free to contribute!

Posted by jtaylor in Business Process Management • Decision Technologies • SOA |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/2922

Comments Post a comment




Remember Me?

(you may use HTML tags for style)

We ask that you type your code (displayed below) in the text box.This code is an image that cannot be read by a machine. It prevents automated programs from submitting comments.


Code:



Most Recent ebizQ Blog Entries
ADVERTISEMENT
This Work
Accountability:The opinions expressed in this blog are solely representative of the blog's author, and not of ebizQ

Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
Your E-mail Address:
BAM: The Killer App for CEP
Date: Feb 12, 2008
Time: 12:00 PM ET
(17:00 GMT)

I WANT TO ATTEND
Event Processing Market Pulse
Date: Feb 14, 2008
Time: 12:00 PM ET
(17:00 GMT)

I WANT TO ATTEND
Archived Webinars | Upcoming Webinars

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map