tag:blogger.com,1999:blog-9203557.post8085025219721058854..comments2023-09-27T14:38:58.735+01:00Comments on Mark Little's WebLog: Heuristics, one-phase commit and compensationsMark Littlehttp://www.blogger.com/profile/15072917010265365428noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9203557.post-43294846935838581222007-09-15T09:33:00.000+01:002007-09-15T09:33:00.000+01:00In some (maybe even many) cases, definitely. "Do t...In some (maybe even many) cases, definitely. "Do this, if it fails do the other, if that's successful do somegthing else ..." is workflow/BPM without a doubt. However, in certain situations like the ones I described, it can be easier/more efficient and more reliable for the TM to try to do the compensation there and then. I've never believed in "one-size fits all solutions" so I'm not considering something to fit all possible use cases. But then the same goes for workflow/BPM. Plus, as we talked before on the subject, at some point you need a reliable coordinator to do this work anyway: whether that's embeddd in a TM or embeddd in a client or workflow or BPM engine doesn't get round that fact.Mark Littlehttps://www.blogger.com/profile/15072917010265365428noreply@blogger.comtag:blogger.com,1999:blog-9203557.post-31916969982763019382007-09-15T05:43:00.000+01:002007-09-15T05:43:00.000+01:00I'm wondering if all this stuff you're talking abo...I'm wondering if all this stuff you're talking about with compensations and heuristic recovery is really starting to bleed into the process management side of BPM. Maybe all these complex scenarios should be modeled instead of coordinated? If you get my drift? Blog on this coming...Anonymousnoreply@blogger.com