• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Cloud computing

Cloud computing






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Cloud computing may futuristic but it is nothing more than a way to pull together proven technologies, including virtualization, SOA, and service management. (Note: Don’t need all three but cloud is most powerful at the intersection where all three technologies converge.) The central ideas of the Cloud Computing model: 1. Abstraction maximizes the benefit of skills and expertise. It decouples the user from operational details, allowing them to focus on high-value work 2. Virtualization allows the complex IT environment to be managed as one single large resource providing services 3. Dynamically allocation provisions, configures, reconfigures, and de-provisions IT capability as and when needed, transparently and seamlessly That’s the big picture for cloud. Tie back to the three examples outlined earlier. Celerity (speed) and reliability is achieved through standardization, where commonly used configurations are stored in a catalog, ready for automatic deployment, reducing downtime and error rate flexibility is achieved through virtualization, smart resource sharing and allocation. It anticipates needs and uses the most appropriate resource to address the need, With complete control over the environment, it can pool resources together and react to unexpected demand. efficiency is achieved through better automation, standardization, and prioritization, minimizing processing time and matching the best resources with the most important and difficult tasks Transition line : Let’s look at the impact of cloud in a real-life scenario.
  • Also: According to Gartner , "Worldwide total software revenue for software as a service (SaaS) within the enterprise software markets is projected to surpass $5.1 billion in 2007 , a 21 percent increase from 2006 revenue. The market is poised for strong growth through 2011, when worldwide revenue will reach $11.5 billion." – M2 Presswire – September 2007 Gartner says that 25% of the whole enterprise software industry, will be software as a service by 2012 and that’s right around the corner. Despite the current economic downturn, the software industry is poised for growth in 2008, with worldwide enterprise software revenue totaling $190.7 billion in 2008, an 8.2 percent increase from 2007 revenue of $176.3 billion, according to Gartner, Inc. – Business Wire, February 2008
  • Consulting methodogies – business SOA – for technology What does it yield – and what is the impact (Give an example – self service provisioning) At IBM, we have been working on a maturity model and process for achieving desirable stages of maturity, a model called the Service Integration Maturity Model (SIMM). The level of de-coupling and amount of flexibility achievable at each stage of maturity are what make up the following seven levels of maturity: Silo (data integration) Integrated (application integration) Componentized (functional integration) Simple services (process integration) Composite services (supply-chain integration) Virtualized services ( virtual infrastructure) Dynamically reconfigurable services (eco-system integration) Each level has a detailed set of characteristics and criteria for assessment, and what follows is a brief description of the highlights of each level: Silo : The organization starts from proprietary and quite ad-hoc integration, rendering the architecture brittle in the face of change. Integrated : The organization moves toward some form of EAI (Enterprise Application Integration), albeit with proprietary connections and integration points. The approaches it uses are tailored to use legacy systems and attempt to dissect and re-factor through data integration. Componentized : At this level, the organization componentizes and modularizes major or critical parts of its application portfolio. It uses legacy transformation and renovation methods to re-factor legacy J2EE or .NET-based systems with clear component boundaries and scope, exposing functionality in a more modular fashion. The integration between components is through their interfaces and the contracts between them. Services : The organization embarks on the early phases of SOA by defining and exposing services for consumption internally or externally for business partners -- not quite on a large scale -- but it acts as a service provider, nonetheless. Composite Services : Now the organization extends its influence into the value chain and into the service eco-system. Services form a contract among suppliers, consumers, and brokers who can build their own eco-system for on-demand interaction. Virtualized Services : The organization now creates a virtualized infrastructure to run applications. It achieves this level after decoupling the application, its servcies, components, and flows. Now the infrastructure is more finely tuned, and the notions of the grid and the grid service render it more agile. It externalizes its monitoring, management, and events (common event infrastructure). Dynamically Reconfigurable Services : The organization now has a dynamically re-configurable software architecture. It can compose services at run-time using externalized policy descriptions, management, and monitoring. The business domain looks primarily at three things: the maturity of the business architecture, the relationship between business and IT and the business value achieved by moving to a service-oriented paradigm. We assess the business architecture and IT support of service orientation with the goal of improved reuse and flexibility, reduced complexity and time-to-market and in both business architecture and IT solutions. The organization domain looks at the maturity of the enterprise and/or business units in the context of organization structure, processes, mechanisms, learning and knowledge enablement, and governance in support of service orientation. This includes the ability to deliver on changing business requirements. The method domain looks at the maturity of the enterprise and or business units in their use of specific software (system) development method and process to support the SOA life-cycle and methods. This includes project management and project estimation considerations for the development of services, components and flows for the SOA life-cycle. The application domain looks at the maturity of the application portfolio to leverage service orientation. It focuses on the use of services for sharing and reuse of business functionality across business units and the ability to flexibly interchanging functionality to meet changing business needs. The architecture domain looks at the maturity of various levels of the architecture including, the enterprise and application architecture to support service orientation. The information domain looks at the maturity of the information and data architecture and management to support service orientation. It includes the notions of information as a service and the ability to apply best practices such as MDM and appropriate application of best practices such as Data Cleansing and Migration. The infrastructure domain looks at the maturity of the infrastructure, monitoring and management in areas of service monitoring and management, service security, and service virtualization. Designing the infrastructure to support the non-functional and operational requirements and service-level agreements needed to operate in a specific scope of the service eco-system.
  • Massive number of services To massive number of users With quality of service
  • Futures: SQL – Structured Query Language (Microsoft Database product Oracle – Database SOE – Standard Operating Environment – Proposed standards for application software ESM – Enterprise System Management – Standard system control software – Remote operations and reporting LAMP – Linux, Apache, MySql, PHP (or Perl) – Standard Web design suite for Linux – RedHat or Suse
  • GCDS: GIG Content Delivery Service EFDS: Enterprise File Delivery Service JIPM TSP/GBS IW PS4 UVDS – Unified Video Delivey Service Consumer RIA Clients

Cloud computing Cloud computing Presentation Transcript