Or how to connect the architecture dots to support a smart connected planet.
The notion of a connected planet is far from new. However, the number of
connections as illustrated in figure 1 is growing at an exponential rate, and
it is fast becoming a reality in which many organizations must operate.
However, I doubt many organizations are preparing for this in a systematic
way. More likely, experience suggests that dozens of connected ‘solutions'
will permeate the organization via myriad routes and just add to the
complexity of the business and IT landscape, becoming yet more spaghetti that
someone is left to untangle.
Architecture is key to dealing with this. However, architectural practices
must evolve to themselves become more connected, and not a set of isolated
disciplines as they are often practiced today. Hence, in this note as well as
considering ... (more)
Cloud Computing is intrinsically service-based. But this is not just in the
highly generalized sense of the term ‘service’, but also in the more
specific Service Oriented Architecture (SOA) use of the term, where
capabilities are provided via published service interfaces. In this research
note we consider why SOA should not be forgotten just because more
fashionable terms have risen to the top of the toybox.
It might be easy to conclude that SOA was yesterday’s issue. In fact
according to some pundits SOA is dead and business transformation,
application and IT modernization, and... (more)
Given its prominence in any discussions around SOA for several years, you
might think that by now everyone has acquired an Enterprise Service Bus
(ESB). However, it is clear that there is still ongoing discussion about
the need for an ESB, and questions still remain as to what exactly an ESB
is. Cloud computing seems to have renewed interest in the topic. In the
same way that people asked "do I need an ESB to do SOA?", we now have "do I
need an ESB to do Cloud Computing?" (at least amongst those who recognize
that Cloud Computing is largely service-based).
I sometimes think a b... (more)
A Reference Architecture (RA) “should” provide a blueprint or template
architecture that can be reused by others wishing to adopt a similar
solution. A Reference Model (RM) should explain the concepts and
relationships that underlie the RA. At Everware-CBDI we then use the term
Reference Framework (RF) as a container for both. Reference architectures,
models and frameworks help to make sense of Cloud Computing.
Unfortunately, such formality is absent from the various reference
architectures, models and frameworks that have been published for Cloud
Computing; t... (more)
The concept that Services are provided ‘somewhere in the cloud’ has
always been central to our vision of SOA and we often used the cloud metaphor
to illustrate this. Some 15 years ago in our early CBD research at Texas
Instruments Software we presented the notion of application solutions
assembled from a ‘cloud of services’ though this was positioned more as a
way to achieve technology independence as the notions of a public
infrastructure provided in the cloud were not well developed then.
The arrival of Web Services at the turn of the millennium provided a
standardized mechanis... (more)