On CNET: Start your holiday tech shopping
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 7 of 19:
Next »
« Previous
Doesn't relational belong in the DB tier?
This whole service orientated architecture stuff adds nothing new at all, only a means of describing and manipulating that is markedly less complete and less flexible than the relational model (ie XML).

Not sure what your gettin at other than you like relational technology. Isn't relational primarily a two tier model? SOA would basically be an n-tier model! You are free to use pure relational on the back end just hide the details at the interface to the consumer to increase reusibility options (at the sake of performance).

Say two companies want to participate in a supply chain application. Walmart let's say wants to interface to Sun. Let's say Sun is Oracle Relational based and Walmart uses the fancy Tamino XML DB. They will want to have a layer between their companies which insulates themselves both from each other and from future enhancements to their solutions. If they go pure relational a simple change in the schema has to be propagated out to all clients ... a maintenance problem. If they go with a "translation/intermediation" layer then they can upgrade the pieces which need it and leave the old pieces in place. Adds extra layers which slows some things down, but the layer can be reused by multiple presentation layers so it adds structure and lowers life-cycle costs.

From the article:

This concept of "loose coupling," in which applications automatically link to one another as needed, gives company data centers much more flexibility by allowing them to reuse integration code in different business processes. A developer could write a service to connect a supply chain to a sales application, and reuse that same integration service to feed data from the supply chain system to a Web portal application. With traditional middleware, each new connection would require significantly more coding, analysts said.
Posted by: oldskool   Posted on: 04/02/04 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Services support  Enterprise Analyst | 04/01/04
Why SOA is the wrong approach  jorwell | 04/01/04
SOA is encapsulation not data replication  oldskool | 04/01/04
SOA, deeply inflexible too  jorwell | 04/01/04
Declaritive programing big part of this stuff  oldskool | 04/02/04
I still don't get it  jorwell | 04/02/04
Doesn't relational belong in the DB tier?  oldskool | 04/02/04
too broad  jhayzee | 08/11/05
Another "new" bandwagon folks. All aboard!!!  No_Ax_to_Grind | 04/01/04
no kidding - no pay to play for me thanks  V Sanders | 04/01/04
No Ax your getting old, time to retire to that  BXLE | 08/13/04
Another PR spin  KeithRisler | 04/01/04
millions of dollars  V Sanders | 04/01/04
lets not be too hasty  V Sanders | 04/01/04
Totally the wrong priorities  jorwell | 04/02/04
Totally the wrong priorities  jorwell | 04/02/04
First step to replace is decouple  oldskool | 04/02/04
SOA is a natural progression  bykerk | 04/23/04
Same old Client Server Architecture - ReBaked  aesjr44 | 09/08/04

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement
  • Smart Tech Expert advice on innovations in healthcare and the green technologies that make it happen. Find out more
  • Smart Business Discussion and advice on management issues that revolve around making your world smarter and more useful. More Smart Advice
  • Smart People The best and worst moves in the management and strategy trenches. Learn More