Over the past few years I’ve been helping a lot of government clients
design and implement architectures for information-sharing. When it comes
to information-sharing one of the most important aspects is the relationships
in the data being shared because it’s those relationships that provide the
context to help you understand and utilize the information better. Within
an enterprise, key data types are often dispersed across multiple systems so
a lot of the things we did included implementing data services (i.e.
SOAP/WSDL-based Web Services) on top of each of these systems to provide
shared access to the underlying data. While this approach does help share
the systems’ underlying data with the rest of the enterprise, you still end
up with these web services providing ... (more)
The popularity of widgets these days has brought to attention the need for
interoperability, i.e. for widgets developed for one site or platform to be
able to run in other sites and widgets developed by different people to be
able to work with each other.
So much so that I know of at least 3 somewhat competing specifications for
widgets.
There's the gadget portion of the OpenSocial specs... (more)
I've recently asked one of my developers to research some integration and
middleware technologies for a project we're working on. After spending a
couple days on this, he said to me "these things are all part of ESBs now" -
i.e. all the integration and middleware vendors have pretty much taken these
capabilities and bundled them into their ESB platforms.
"Oh you need a message bus? That's ... (more)
There are a variety message exchange patterns that can be used to implement
an SOA. Know them and when to apply them. It can mean the difference between
an SOA that scales and performs vs. one that doesn't. The traditional
synchronous request/response may not always be the most appropriate in all
scenarios. Here are some examples of other types of MEPs:
Asynchronous request/response using ... (more)
There are a variety message exchange patterns that can be used to implement
an SOA. Know them and when to apply them. It can mean the difference between
an SOA that scales and performs vs. one that doesn't. The traditional
synchronous request/response may not always be the most appropriate in all
scenarios. Here are some examples of other types of MEPs:
Asynchronous request/response using ... (more)