| Share this post! | Vote this! |
|
If you've been around the enterprise software industry the last few years, no doubt you've heard the term "service oriented architecture" (SOA). If you aren't technical, it's one of those terms that flies right over your head. That's understandable, given that most definitions of SOA are rather dry. For example:
A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. (OASIS)
Further complicating the topic is a dictionary-sized list of related technical acronyms such as SOAP, XML, CORBA, DCOM, .NET, J2EE, REST, BPEL and WS-CDL. The list goes on…
colloquial definition of SOA:
A new and better way to get a bunch of different software programs to work together so people can do things that require information from each of those systems.
More...
A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations. (OASIS)
Further complicating the topic is a dictionary-sized list of related technical acronyms such as SOAP, XML, CORBA, DCOM, .NET, J2EE, REST, BPEL and WS-CDL. The list goes on…
colloquial definition of SOA:
A new and better way to get a bunch of different software programs to work together so people can do things that require information from each of those systems.
More...
0 comments:
Post a Comment