When dealing with application integration, as you know by now, we are dealing
with much complexity. The notion of ontologies helps the application
integration architect prepare generalizations that make the problem domain
more understandable. In contrast to abstraction, generalization ignores many
of the details and ends up with general ideas. Therefore, when generalizing,
we start with a collection of types and analyze commonalities to generalize
Clearly, semantic heterogeneity and divergence hinders the notion of
generalization, and as commonalities of two entities are represented in
semantically different ways, the differences are more difficult to see. Thus,
ontological analysis clears the ground for generalization, making the
properties of the entities much more clear. Indeed, ontological analysis for
application integration encourages generalization. Th... (more)
The notion of building bridges to service providers and managing the
interaction will become more commonplace in 2006 as we learn to accept that
many services we leverage within an enterprise are services we may not host.
The technology exists today. We need to define and refine our approaches now,
including architectures, enabling technology, and use of standards. Most
enterprises are way behind.
We are moving toward a day when most of our enterprise applications may be
delivered as services, and thus provide a more economical way to approach
information technology management w... (more)
There is a lot of talk about how SOA will significantly lower the need for
developers, thus the savings of SOA. This will be accomplished through the
promise of reuse that's driving many toward the SOA light. However, I'm not
sure we'll see a reduction in development with the advent of SOA, but perhaps
rather a redistribution of talent in the longer term. At the end of the day,
the reason for leveraging SOA is agility. Reuse and development savings are a
secondary benefit, if they happen at all.
Truth be told, we've been considering the demise of the developer during many
"hype ... (more)
So what's hot these days in the world of SOA? Governance, registries,
orchestration...? Nope. As folks looking to implement SOA seek that first
killer project the emphasis is on what to do, not what you use, and that's
exactly the right way to think. As SOA becomes more of a reality among the
Global 2000, the focus on discipline as a concept will be as important as
solutions, perhaps more important than many expect. Let me explain.
This is a clear trend that I see in the SOA space, those charged with
building SOAs in their enterprise are working on establishing approaches to
Here we go again. While the paint is still wet on this new Web 2.0 stuff,
many SOA vendors and large analysts firms are calling their market SOA 2.0.
It's one of the silliest things I've heard in a long while, and both the
analysts and vendors who use this term should be ashamed of themselves.
I get Web 2.0 because the Web is well over 10-years-old and we've been
successful in using this pervasive technology and now we're moving to newer
and more exciting stuff such as AJAX and RSS thus the new version number.
However, we've yet to get large-scale traction with SOA so SOA 2.0 is ... (more)