Hi all,

Not to self post, but I wrote a blog piece called "Business Logic is
not Monolithic" on this topic a while back:

http://www.soacenter.com/?p=34

I think this whole discussion about "reuse" though is just a piece of
the puzzle. The real challenge is to enable a model where multiple
policy sources can assert their own logical constraints on a system
and to have those constraints enforced and reconciled.

Miko

--- In [email protected], Keith
Harrison-Broninski <[EMAIL PROTECTED]> wrote:
>
> Anne Thomas Manes wrote:
> 
> > The advice I give to my clients is to start their reuse efforts with 
> > infrastructure functionality -- things like authentication, 
> > authorization, auditing, cryptography, logging, monitoring, caching, 
> > etc. One of the things I like best about SOAP is that it enables
clean 
> > separation of infrastructure from business logic via the SOAP 
> > mediation model.
> 
> Thanks for this Anne.  You're quite right, of course -
infrastructure is 
> well suited to reuse via SOA techniques.  However, to my mind this 
> raises yet another set of questions.  Your examples, particularly that 
> of terrorist checking, suggests that some aspects of infrastructure 
> /are/ business logic.  In fact, which types are not?  All the functions 
> you list above are required by the business, or the IT department would 
> have no justification for implementing them.
> 
> Perhaps there are different "types" of business logic, the 
> infrastructure "type of business logic" being logic that is driven by 
> organizational concerns rather than process design issues - a matter of 
> policy rather than procedure, if you like.  If so, your viewpoint as 
> expressed above suggests that the former type of functionality may be 
> better suited to re-use via SOA.
> 
> It is interesting to consider this question from a process design point 
> of view - it suggests the use of an aspect-oriented approach to process 
> design to capture such cross-cutting concerns.  Aspect-orientation has 
> not been a feature of process design techniques to date.  Perhaps it 
> should be ...
> 
> -- 
> 
> All the best
> Keith
> 
> http://keith.harrison-broninski.info
>









 
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/
 



Reply via email to