> <<The widespread implementation of service-oriented architectures has
> shown that we have moved past the early adoption phase.
First comment: What's with all this widespread adoption business
that's going on? I would agree that we have widespread interest and
attempts to adopt, but I think if they surveyed CEOs or other non-IT
personnel about SOA adoption, we probably wouldn't say it's anywhere
near widespread. I've always seen SOA as a minimum of a 5 year
journey, so this talk seems a bit over-hyped to me.
> The key to a BRMS is the use of a centralized rules
> repository, within which resides the decision logic that applications
> use.
Second comment: Has anyone actually successfully utilized a BRMS
without killing performance? The way this author talks, every single
clause within an if-then block should be externalized. You can't get
more fine grained than this. I definitely agree that we should
attempt to externalize rules that change frequently, but if you go to
far, you'd better have a good caching architecture for them, because
making a distributed call for every decision point is just scary.
-tb
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
