| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SOA is Dead |
« View previous topic :: View next topic » |
| Author |
Message
|
| RogerLacroix |
 Posted: Tue Jan 13, 2009 11:01 am Post subject: SOA is Dead |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
I don't know if anyone else read this blog: "SOA is Dead; Long Live Services" but it appears to have started an interesting fire-storm on the internet.
http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html
I wonder if IBM will soon drop the "SOA" from the Impact conference?
Generally speaking, I don't play in the SOA space but I do firmly believe in the "Long Live Services" philosophy.
Back in the late 80's, I joined the middleware group at Royal Bank of Canada (the largest bank in Canada). The middleware interfaced/interacted with exposed application APIs (aka services). This was a company-wide infrastructure approach and seemed very logical. I just assumed all large companies did it this way.
In the late 90's, I joined Candle and travelled to lots of companies and was shocked that most companies had "islands" of application. It just seemed so illogical and anti-productive (and a waste of the company's money). But to my shock, most companies operated this way.
Candle even created a product called Roma (later renamed to eBP - eBusiness Platform) to get companies to by into the "services" concept. Most senior architects liked the concept but CIOs and VPs just would not spend the money to rewrite applications (they could not see the RIO). Even on projects were the CIOs had bought into the "services" idea, the client's application developers were sometimes very resistant to the change (fear of job lose or fear of the unknown). So, the "services" concept was a very hard sell.
For the last 20 years, I have firmly believed in "decoupled services" (and reusable services) when an application gets built. Every 5 years, the IT industry goes "ga ga" over an acronym and in the end, it fades from memory. Hence, architects/developers should build their applications with a service (or API) so that it can be used by other applications (and don't worry about the latest trend). And of course, the WMQ should be used as the messaging bus.
Anyway, that's my two cents.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| manicminer |
| Posted: Wed Jan 14, 2009 3:28 am Post subject: |
|
|
Disciple
Joined: 11 Jul 2007
Posts: 177
|
Strange blog, seems like the usual sort of trolling you see on blogs designed to get lots of visitors and up the advertising revenue / make a name for yourself.
SOA is Service Oriented Architecture.
If services are good, then by definition SOA is good. SOA is simply designing an architecture for system communication based around a service concept.
People may sell products that are branded SOA to try and leverage a popular buzz word to get more sales, or to ensure that people know that those products are designed to help with building SOA based systems, but that doesn't make the SOA approach bad.
What you state in your last paragraph is exactly what SOA is all about, it is about building decoupled, reusable services and in most cases having those services talk to each other over some form of messaging bus.
People may dislike the buzz word, but it doesn't change the intention, don't throw the baby out with the bath water. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 14, 2009 8:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The very first line of the "SOA is dead..." article:
| Quote: |
| Once thought to be the savior of IT, SOA instead turned into a great failed experiment—at least for most organizations. |
Over the decades there have been other saviors of IT that have, for better or worse, come and gone. 4GLs had their hayday, JAVAs destiny remains to be seen.
I have no issue whatsoever with SOA as a design/development philosophy, or using JAVA to get the benefits of code reusability.
But, with limited budgets and shrinking time constraints, I am hard-pressed to recommend re-architecting existing applications today for even the most glowing potential benefits that might be realized tomorrow.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
