• This is a community for Developers who use OOPS Concepts in their daily development processes.    Login to Ask Questions
• Here you will find various resources around OOPS Concepts.
• Tips from experienced Developers and Architects on OOPS! Post Your Tip
• You are welcome to share your experience with using OOPS in your development. Share Now

By Dave Chappell

Myth #1. ESB is just a new name for EAI.
While many IT architecture groups are focusing on building SOAs, they still inevitably beg the question of "how is ESB different from EAI?" An ESB is an infrastructure for building an enterprise SOA, and is capable of being used in a more general way than a conventional EAI broker. According to Forrester Research, an ESB helps enterprises obtain the value of SOA by increasing connectivity, adding flexibility that speeds change, and providing greater control over use of the important resources that it binds.

Web-oriented architectures are easier to implement and offer a similar flexibility to SOA.

By Roger Smith

CIOs and system architects find themselves stymied as they try to sledgehammer complex SOAs into their enterprises. Top-down, "if you build it, they will come" approaches to service-oriented architecture often wind up failing--sometimes spectacularly. Instead of better aligning business processes and IT departments, as was promised, too many employees remain oblivious to expensive SOA initiatives. And those optimistic ROI projections? Forget 'em.

SOA Repository Best Practice
By: John Moe, Head of Business Integration, TORI Global
Tuesday, December 8, 2009

For those of us who have been developing applications for many years (think COBOL & Assembler from the 70s and 80s), the idea of having a code library (programs and routines) is nothing new. However for the Web Services generation, this concept has taken a while to re-emerge, but has now been packaged in the form of a services registry and/or repository.

In the late 1990’s several methodologies began to get increasing public attention. Each had a different combination of old ideas, new ideas, and transmuted old ideas. But they all emphasized close collaboration between the programmer team and business experts; face-to-face communication (as more efficient than written documentation); frequent delivery of new deployable business value; tight, self-organizing teams; and ways to craft the code and the team such that the inevitable requirements churn was not a crisis.

http://www.agilealliance.org/show/2

Jack Milunsky

I may have blogged about this previously. I have written so many blogs, I can't recall any more. However questions regarding Sprint length surface on the forums regularly.

As per usual, the answers one must give always depends on the context and every context is different than the next. So let me start with the context - this is an excerpt of a post on the scrum development group on Yahoo. Incidentally, Yahoo groups is a good place to hang out. You learn a lot from all the questions and the different contexts facing teams around the world.

The Context

Management Strategies for SOA
By: Mike Kavis, CTO/Chief Architect, M-Dot
Tuesday, October 13, 2009

Management Strategies for SOA

The SOA consortium has been running an annual contest for the best SOA Case Studies. Last year I attended the event and summarized the common characteristics of successful SOA implementations. This year's winners shared the same characteristics:

1. Strong executive level commitment
2. Educate the business of the value of SOA
3. Establish a Center of Excellence
4. Well defined business services
5. Completeness of services

Hi Guys,

Here is a free eBook, "SOA for Dummies". Free for Download

Thought it will be useful. Have a look.

https://www14.software.ibm.com/webapp/iwm/web/signup.do?source=swg-soafd...

SOA is exciting dont you think?

What is the use of Abstract class