Re: Can the App Layer be used to communicate between two domains or can two Doma

I think the app layer should orchestrate tasks that the user has to
get done, and any associated state, like the progress of the task, etc.

If the domains are truly separate, then I would still use an
Anti-Corruption Layer, because Domain Services should focus solely on
their host domain models. Their inputs and outputs should be in terms
of only one model.

--- In domaindrivendesign <at> yahoogroups.com, <ashley.fernandes@...> wrote:
>
> Hi ,
> 
>  
> 
> Thanks for the reply...J
> 
>  
> 
> Yes....you are perfectly right about the anti corruption layer.....hence
> we(Loans) have used adapters when communicating with another domain
> 
>  
> 
> My question is actually slightly different.......Can Should Different
> Domain Services talk to each other (diff domains) or should the
> application services actually  orchestrate the communication between two
> diff domains (via adapters of course)
> 
>  
> 
>  
> 
> Thanks & Regards
> 
> Ashley
> 
>  
> 
> Ashley Fernandes
> 
> Consultant | Banking Products Division | Goregaon Annex, Mumbai
> 
> Direct: +91 22 6718 7421| Mobile: +91 9820842428 
> 
>  
> 
> i-flex solutions has proposed to change its name to Oracle Financial
> Services 
> 
> (read more about the proposed name change at www.iflexsolutions.com
> <http://www.iflexsolutions.com/> )
> 
>  
> 
> From: domaindrivendesign <at> yahoogroups.com
> [mailto:domaindrivendesign <at> yahoogroups.com] On Behalf Of moffdub
> Sent: Wednesday, August 13, 2008 4:31 AM
> To: domaindrivendesign <at> yahoogroups.com
> Subject: [domaindrivendesign] Re: Can the App Layer be used to
> communicate between two domains or can two Doma
> 
>  
> 
> Hi,
> 
> The draconian way to do this would be an Anti-Corruption Layer. This
> assumes that the three domains evolve relatively independently of each
> other.
> 
> The other way that comes to mind is not to segregate your application
> layer into Loan App Layer, Global App Layer, and Security App Layer.
> Have a unified App Layer that addresses the three domain models. 
> 
> I think the choice depends on just how segregated the domain models
> are. The more independent and disparate they are, the more you should
> lean towards some Anti-Corruption Layers.
> 
> --- In domaindrivendesign <at> yahoogroups.com
> <mailto:domaindrivendesign%40yahoogroups.com> , <ashley.fernandes@>
> wrote:
> >
> > Hi All,
> > 
> > 
> > 
> > We have three domains , namely Global, Security and Loans, had two
> > requirements,
> > 
> > 
> > 
> > 1) My Loans Account Need to get information from my global
> > domain...like Bank, Branch Information etc....Should my Loans
> > Application Service(Loans App Layer) talk to the Domain Service of my
> > Global Domain(Global Domain Service) (via an adapter that resides in
> my
> > loan app layer)? or should my Loans Domain Service (Loans Domain
> Layer)
> > talk directly to my Global Domain Service (Loans Domain Layer)
> > 
> > 
> > 
> > 2) For Authenticating the users using the Loans Domain Service ,
> > Again similar query, should my loans app layer talk to the Security
> > domain via an adapter or can my Loans Domain Services directly talk to
> > the Security Domain?
> > 
> > 
> > 
> > Thanks & Regards
> > 
> > Ashley
> > 
> > 
> > 
> > Ashley Fernandes
> > 
> > Consultant | Banking Products Division | Goregaon Annex, Mumbai
> > 
> > Direct: +91 22 6718 7421| Mobile: +91 9820842428 
> > 
> > 
> > 
> > i-flex solutions has proposed to change its name to Oracle Financial
> > Services 
> > 
> > (read more about the proposed name change at www.iflexsolutions.com
> > <http://www.iflexsolutions.com/> )
> > 
> > 
> > 
> > 
> > 
> > DISCLAIMER:
> > This message contains privileged and confidential information and is
> intended only for an individual named. If you are not the intended
> recipient, you should not disseminate, distribute, store, print, copy
> or deliver this message. Please notify the sender immediately by
> e-mail if you have received this e-mail by mistake and delete this
> e-mail from your system. E-mail transmission cannot be guaranteed to
> be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete or contain
> viruses. The sender, therefore, does not accept liability for any
> errors or omissions in the contents of this message which arise as a
> result of e-mail transmission. If verification is required, please
> request a hard-copy version.
> >
> 
>  
> 
> 
> 
> DISCLAIMER:
> This message contains privileged and confidential information and is
intended only for an individual named. If you are not the intended
recipient, you should not disseminate, distribute, store, print, copy
or deliver this message. Please notify the sender immediately by
e-mail if you have received this e-mail by mistake and delete this
e-mail from your system. E-mail transmission cannot be guaranteed to
be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete or contain
viruses. The sender, therefore,  does not accept liability for any
errors or omissions in the contents of this message which arise as a
result of e-mail transmission. If verification is required, please
request a hard-copy version.
>

------------------------------------