This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
What is Service Oriented Architecture? this has been asked to me in one of the Interview.
what I understand by SOA is -- SOA is a set of rules(or specifications) applicable to the web services available and effectively making use of them. below are the set of some rules please update/add if i am wrong
1.) every service should do only one task and stick to it
2.) a service should not call any other service with in it. calling another service (based on some criteria) should be left to Integration tool.
and many more like this...can some one tell me what SOA is (if my above understanding is wrong). is it specified in the form of a diagram of some thing like that please share it
SOA means a change in the perspective how the enterprise looks at their IT solutions. Instead of creating isolated applications they think in reusable services. Once a solution is needed it can be modeled as a business process and can be composed from existing and/or new services.
(For sure there are many other ways to describe it.)