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 part of our ESB now." "Oh you need this
adapter? That's included in our ESB."
In most cases when you're implementing an SOA, you will need some piece of
middleware or integration technology. With just about every vendor making
these things part of their ESB suites, you're probably gonna end up getting
an ESB even if you don't need a whole freakin' ESB. That's why all SOAs need
ESBs (rega... (more)
HATEOAS or “Hypermedia As The Engine Of Application State” is one of the
core principles of REST and it essentially boils down to having links in the
representations of your resources. How to apply this principle in the
design of a service and the benefits that it provides depend on the nature of
the service you are building, i.e. whether your service is more
process-centric or data-cen... (more)
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, ke... (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)
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)