Could not a service run periodically, without any external calls?

 

-- 

Udi Dahan - The Software Simplist

 

From: [email protected]
[mailto:[email protected]] On Behalf Of
Michael Poulin
Sent: 23 December 2008 11:50
To: [email protected]
Subject: Re: [service-orientated-architecture] Re: Yefim Natis is sure that
"SOA is integration"

 

Here is a misunderstanding, Rob. Certainly, to run, a service needs an
external call. However,  self-contained atomic SOA business service does not
need any other business services to provide its RWE; it does not know about
outside world of services. In contrast, an aggregate service - does.

- Michael

 

  _____  

From: Rob Eamon <[email protected]>
To: [email protected]
Sent: Tuesday, December 23, 2008 4:01:52 AM
Subject: [service-orientated-architecture] Re: Yefim Natis is sure that "SOA
is integration"

--- In service-orientated-
<mailto:service-orientated-architecture%40yahoogroups.com>  architecture@
yahoogroups. com, Michael 
Poulin <m3pou...@.. .> wrote:
>
> Integration with what?
> 
> Assume, we have a self-contained atomic SOA business service. It 
> does not need anything outside its boundaries to perform announced 
> business functionality and provide for the RWE. 

Oh yes it does. A service all by itself does nothing. Without some 
external stimulus, it does nothing at all.

Something outside of the service must call it via one of the exposed 
interfaces or the service will do nothing whatsoever.

> Certainly, it has to run in an execution environment and it 
> integrates with it. However, it does not integrate with an 
> orchestration or a process that uses it because it perfectly 
> functions alone. 

The orchestration or process integrates with the service by 
connecting to and invoking one of the service's exposed interfaces.

> Invocation of such service does not generate any new business value.

Invocation of a service is required to generate any busines value. A 
service uninvoked is a useless pile of bits.

> As I responded to Rob, if a SOA service does not have an interface 
> for particular type of communication channel, does it " have 
> intrinsic seamless integration capabilities" ?

No. But then how did the architect miss that channel? But for the 
channels/interfaces that are not missing, the system has intrinsic 
integration capabilities. 

> So, integration is just a link system between participants (may be 
> one link for 2 participants) . Connecting those participants we do 
> not create a SOA system, or we do?

Connecting participants creates an integration. Creating an "SOA 
system" (a term I loathe) requires creating service providers with 
separately standing interfaces that are invoked within an execution 
context by service consumers. Consumers integrate with providers via 
the agreed upon interfaces.

-Rob

 

 

No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.0/1861 - Release Date: 22/12/2008
11:23

<<image001.jpg>>

<<image002.jpg>>

Reply via email to