With the advent of Web services and SOA, we've been seeking to create
architectures and systems that are more loosely coupled. Loosely coupled
systems provide many advantages including support for late or dynamically
binding to other components while running, and can mediate the difference in
the component's structure, security model, protocols, and semantics, thus
This is in contrast to compile-time or runtime binding, which requires that
you bind the components at compile time or runtime (synchronous calls),
respectively, and also requires that changes be designed into all components
at the same time due to the dependencies. As you can imagine, this type of
coupling makes testing and component changes much more difficult.
The advantages of loosely coupled architectures, as found within many SOAs,
are apparent to many of us who have built ar... (more)
Many organizations out there don't really have to sell SOA. They understand
that hype is the driver, and, in essence, leverage the thousands of articles
and books on the topic to sell this architectural pattern.
However, in most cases SOA has to be sold in the enterprise. If you're doing
SOA right, you'll find that the cost quickly goes well into the millions, so
you'll need executive approval for that kind of spending. However, the
benefits are there as well, including the core benefit of agility that could
save the company many times the cost of building a SOA. Or, at least, tha... (more)
So, what do AJAX and SOA have in common? The answer: Everything.
Is AJAX an enterprise technology? The answer: Absolutely.
As we move to next-generation enterprise architectures using newer notions
such as Service Oriented Architecture (SOA), there's a need for a dynamic Web
interface that can layer over services and provide more value to the
enterprise. Moreover, the enterprise in general can benefit from the
advantages of AJAX; it's just a matter of making enterprise developers as
well as the SOA architects aware of AJAX.
AJAX is becoming the standard dynamic interface for the W... (more)
Although a number of standards exist for information interchange and process
definition, industry standards have yet to emerge for defining common
integration server and B2B integration server services such as routing, rules
processing, and transformation. In the absence of such standards, individual
vendors have created proprietary approaches to these basic
information-processing services. As a result, we are confronted with features
that are not interchangeable, require specialized training, and do not
provide a common framework of services.
Even as we begin to implement stand... (more)
Many in the world of application integration have begun to adopt the notion
of ontology (or the instances of ontology: ontologies). Ontology is a term
borrowed from philosophy that refers to the science of describing the kinds
of entities in the world and how they are related.
Ontologies are important to application integration solutions because they
provide a shared and common understanding of data (and, in some cases,
services and processes) that exists within an application integration problem
domain, and how to facilitate communication between people and information