Subject: Subsystems communication 2004-10-20 - By Chris Rowse
Back
Hi,
I am presently busy with scoping and sizing an application and am
finding that by going SOA using Web services, there is little or no
differnce between interfaces in these dimensions.
It is purely the presentation and nature and authorisation of the
actor that differentiate the two dimensions.
In my case, a banking environment, there are many interface channels.
Substantial cost saving and reduction in complexity can be realised by
treating all interaces orthagonally (e.g. XML over HTTPS).
We are considering ISO / OASIS standards for all communications to
further standardise our interfaces ad make them more interoperable with
third parties.
You also get better decoupling by separating the subsystems across a
clear boundary. This may, and often needs to reflect the areas of
responsibility of the business units involved.
Chris
On Wed, 2004-10-20 at 15:03, Jin Chun wrote:
>
>
> Actually, I disagree somewhat,
>
> IMHO, one should always strive to layer the system 2 dimensionally.
> In one dimension, there are service interfaces that are use case/story
> modeled, and the other,
> are subsystem interfaces that may be reused across application domains,
> e.g. gateways, etc.
>
> Jin
>
> Jin Chun
>
>
> Vice President: Chief Applications Architect
> State Street ??? Global Link | www.statestreet.com | www.globallink.com
> 617.664.1695 | byungchun@(protected)
> SCJA SCJP OCP-DBA
>
>
> Confidentiality Notice: The information contained in the email is intended
> for the confidential use of the above-named recipient(s). If the reader of
> this message is not the intended recipient or person responsible for
> delivering it to the intended recipient, you are hereby notified that you
> have received this communication in error, and that any review,
> dissemination, distribution, or copying of this communication is strictly
> prohibited. If you have received this in error, please notify the sender
> immediately and destroy this message.
>
>
> |-- ------+-- ---- ---- ---- ---- ---- ---- --->
> | | Ryan Wiles |
> | | <ryan.wiles@(protected)> |
> | | Sent by: An interest list|
> | | for Sun Java Center J2EE |
> | | Pattern Catalog |
> | | <J2EEPATTERNS-INTEREST@(protected)|
> | | VA.SUN.COM> |
> | | |
> | | |
> | | 10/19/2004 09:51 PM |
> | | Please respond to An |
> | | interest list for Sun |
> | | Java Center J2EE Pattern |
> | | Catalog |
> | | |
> |-- ------+-- ---- ---- ---- ---- ---- ---- --->
> >-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----|
> |
|
> | To: J2EEPATTERNS-INTEREST@(protected)
|
> | cc:
|
> | Subject: Re: Subsystems communication
|
> >-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----|
>
>
>
>
> Subsystems are a waste of time.
>
> Peace out.
>
>
> > I have a question regarding subsystems communication.
> > How do I integrate a subsystem with dependent subsystems (possibly remote
> > ones)?
> > I found a suggestion saying to call the dependent subsystems Business
> > Delegates/Fa??ades from the top subsystem Business Object. Is this
> correct?
> > I don't feel comfortable with this solution because a think that if you
> are
> > already in the business layer, why should I use a Pattern designed to
> > integrate presenteation-tier clients and system's business services.
> >
> > ===================================================================> >
Companion Site: http://www.corej2eepatterns.com
> > J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> > List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> > Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
> ===================================================================>
Companion Site: http://www.corej2eepatterns.com
> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
> List Archive:
> http://archives.java.sun.com/archives/j2eepatterns-interest.html
> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
> listserv@(protected)
>
===================================================================Companion
Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
