JavaWorld
addict
Reged: 06/20/03
Posts: 482
|
|
What is service-oriented architecture?
|
svaucher
stranger
Reged: 09/08/03
Posts: 7
Loc: Montreal, QC
|
|
It's kind of funny to see concepts over 30 years old being rehashed like separation between implementation and interface, and simple information hidding. If it's because of a new name it's finally accepted, than 1/it's good, and 2/IT'S ABOUT TIME...
It's fun to see how companies will sell system integration with another name.
--------------------
Stephane Vaucher
Web page
|
Hassen
Unregistered
|
|
It's true that separation between implementation and interface is a very very old concept. But make it working with several programming langages was not easy but a tricky work (even with a CORBA like middleware). The goal of SOA is to simplify and automate the developpement (in my opinion).
|
Konmatan
Unregistered
|
|
Perspectives depends on support of this technology by enterprise companies. Now it's to low.
|
Anonymous
Unregistered
|
|
As you say the concept is not fundamentally new. The new part is several standards have evolved and you don't see that often , all the vendors singing the same song. I had a blog entry on the similar subject, Check it out Why do you think SOA will be successful now ?
-raghu
|
svaucher
stranger
Reged: 09/08/03
Posts: 7
Loc: Montreal, QC
|
|
SOA is what large companies (IBM, BEA) are calling integration nowadays. SOA promotes what is a healthy way of separating software in modules that are decomposed by functionality. Acceptance in industry is basically the result of a cost-benefit exercise (cost coming from maintenance) even if from an software engineering standpoint, SOA (not necessarily WS) principles are obviously considered good.
If WS are what interests you, from my talks to an IBM WS guru, the interest behing WS is that it becomes trivial to integrate third-party components.
--------------------
Stephane Vaucher
Web page
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
