service-oriented integration (SOI)
SOI is also an abbreviation for Silicon-On-Insulator.
Service-oriented integration (SOI) is defined as integrating computing entities using only
service interactions in a service-oriented
architecture. Service-oriented integration addresses problems with integrating legacy and
inflexible heterogeneous
systems by enabling IT organizations to offer the functionality locked in existing applications as
reusable services.
In contrast to traditional enterprise application integration (EAI), the
significant characteristics of services-oriented integration are:
Well-defined, standardized interfaces – Consumers are provided with easily-understood and
consistent access to the underlying service.
Opaqueness – The technology and location of the application providing the functionality
is hidden behind the service interface. In fact, there is no need for a fixed services
provider.
Flexibility – Both the providers of services and consumers of services can change - the
service description is the only constant. Provided both the provider and consumer continue to
adhere to the service description, the applications will continue to work.
Contributor(s): Brian Connell, CTO, WestGlobal
This was last updated in September 2005
Email Alerts
Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy
More News and Tutorials
-
In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."
-
Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.
-
This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.
