Ask: what the hell is service-oriented architecture?
Service-oriented architecture (SOA) is the hottest topic in the IT arena. Providing a comprehensive plan to interrelate business with technology, SOA combines the talents and skills of an entire organization, with its requisite needs and computing know-how. Presenting the necessary tools—processes, best practices, and standards—for developing a sound SOA, Service-Oriented Modeling: Service Analysis, Design, and Architecture introduces a service-oriented modeling framework that employs an agile and universal business and technology language to facilitate analysis, design, and architecture initiatives.
I have no clue what that means. I wonder: precisely what is that in terms of actual programs, bits, and bytes? Is it simple, flexible web services? Exposing programs as web services? Web services as a loose coupling technique of disparate systems? Throw me a bone here.
We went through a period of serious introspection and concluded that a service-oriented architecture would give us the level of isolation that would allow us to build many software components rapidly and independently. By the way, this was way before service-oriented was a buzzword. For us service orientation means encapsulating the data with the business logic that operates on the data, with the only access through a published service interface. No direct database access is allowed from outside the service, and there's no data sharing among the services.
[1] - http://www.acmqueue.com/modules.php?name=Content&pa=show...