Documents and files for download. Registration required.
In any given domain, a Reference Framework (RF) provides a common backplane for consistency, collaboration, sharing, and reuse. Without a consistent framework, the domain in question will remain an interesting concept but deliver suboptimal business value. With an appropriate RF the work of individual projects, programs, divisions and partners will be coordinated with just enough formality to ensure that the many moving parts can fit together when and were needed.
A RF is needed to:
- Identify those things that need to be common
- Create consistency where needed
- Indicate where individual projects can diverge from the RF where appropriate
- Provide a structured approach to managing standards, policies, patterns in order to deliver on objectives
This research note provides an overview of the process for the creation and evolution of a RF.
As well as deploying new applications to the cloud, many organizations will also be considering the opportunities to migrate current applications to the cloud in search of reduced costs or SLA improvements. In this research note we consider several migration alternatives, expressed as a set of patterns.
The patterns can also be seen as a sequence of activities, through which the current application is gradually modernized
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.
Moving to Cloud Computing at any level, private, public or hybrid, represents a major challenge and opportunity for enterprises. But for an enterprise getting beyond the experimentation, niche and commodity applications to actually deliver the expected cost benefits with minimum risk is always harder than anticipated. Full blown Cloud adoption implies mature and sophisticated SOA implementation and impacts many business processes and requires coordination of multiple, disparate disciplines. Experience tells us such an adoption process requires integrated business driven strategic planning.
There are a plethora of different reference architectures, models and frameworks for Cloud Computing. Which one should an organization adopt? Of course there’s no straightforward answer to that question and in this research note we provide guidance on how to organize some of the best ideas that are emerging in a practical structure that should stand the test of time.