Intro Cloud Computing

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Infrastructure Integration includes networks, servers, app servers, data bases, web servers, and in my mind, even application installation. These are well defined, usually have their own staff… and they take up a large part of budget/effort, but because they are visible, for the most part, they are accounted for (time-wise). Unfortunately, as we all know, this is just the “setup”… next, you have the magic… The magic of DATA integration

    This is the POINT behind all the infrastructure integration efforts. If not for teasing out information about our data in a way that’s usable, we wouldn’t do any of the other stuff. The other stuff is just necessary evil. It’s the boat ride you have to take to the dive site… it might make you queasy, but you can deal with it because once you get there, you’ll see some neat stuff.

    It’s Data integration that’s hard (and expensive). And, importantly, it’s hard to explain to others, so they discount it.

    This is really less of a definition, and more of putting an edge around a concept. And, that edge doesn’t fully surround the concept, only it gives it some shape.

    This is not really a definition, but it does help keep our eyes on the prize and measure the success we have with it. I prefer to think of it as…

    Of course, I’ve still not defined anything. Just trying to put some parameters around it. I defined integration earlier, now I’m saying turn commodity integration (defined as necessary, but not differentiating) into a utility.

    Talk about thinking outside the box. If email is commodity, everything below it in the infrastructure stack is too. And, of course, this is a great example, in some cases, perhaps email is not a commodity. Perhaps there are some Outlook customizations for sales force automation, ACT plugins or whatever, that makes email a tool instead of a commodity. But, even then, it illustrates the point… using salesforce.com, and email, you want to bring that information together. The more you can do that… the more relevant IT will be. Yet, when each app is a closed silo, where the efforts are on integration rather than connectivity, it becomes a real challenge to leverage the cross-app data and relationships.

    Not talking about ESB- or inter-app style messaging. I’m talking about email messaging. There are messages that are part of the conversation everywhere. But they lose context in email. Yeah, maybe there is a link back to relevant information, but it’s very very basic integration that doesn’t even server technical users well. We want to bring information together. Best example I can think of, however trivial, are those silly facebook messages that say “you have an email” but, I can’t respond, I need to go to facebook and respond. I have messages all over the place, there is no reason why Facebook, LinkedIn, Twitter, Email, Progress, and all these places have different places where I have to go and bring this information together manually.Now, this (messaging) is maybe not important to my enterprise, but other similar things are. How about, customer information. There is customer information all over the place, in the sales force automation system, in the provisioning system, in shipping, maybe in contracts administration, etc. Maybe in multiple places. It’s not just about Master Data Management, and having a uniform customer record (that’s hard too), but it is about having a view on my relationship with the customer so I can make better business decisions.

    If all IT does is integrate (data and processes), it will have to become more disciplined, and there will be time to do so. I believe clouds help us get rid of the low level things IT focus on, to help us raise the bar and focus on what’s important.New classes of applications: Really more mashup-like, rapidly created, possibly with short lifespans, that help users synthesize and visualize relevant data and events so they can better execute the business. Data is no longer locked into the silo. In fact, silos simply disappear and we have a full federation of services.

    This is really less of a definition, and more of putting an edge around a concept. And, that edge doesn’t fully surround the concept, only it gives it some shape.

    Visibility, protect from change, service level management.

    When I was working at Radianz, I was responsible for delivering a middleware layer on top of a shared network. Forget the technology. One of the big problems was around culture and contracts. If the network was up, but the middleware service was down, it was down from the customer perspective, and they’d want a refund. However, the network people were bonused on network uptime, not on middleware uptime, so they didn’t look at it the same way. Then, our customer support needed to be trained not to say “well, the network is up” to the customer, why would the customer care? It wasn’t working from their perspective. This is a hard problem, least so with respect to technology.

    Security needs to change to application or message layer security. Today we rely too heavily upon network layer efforts, and frankly, it’s just not secure enough. We know that, but it’s hard to change. I believe this resistance to change will hinder cloud efforts.

    2 Favorites

    Intro Cloud Computing - Presentation Transcript

    1. Introduction to ‘Cloud Computing’
      చక్రవర్తి
      9/19 - 2009
    2. Expertise level
      Using Computer for email
      Use computer for programmingsince
      0 to 2 yrs
      2 to 4 yrs
      4 yrs and Above
      Will learn later
      I’m here because of my friend / philosopher / blah .. blah ..
      ఏదో.. టైమ్పాస్
    3. What, How and Why
      Do I care
      Why do I care
      I don’t care
      ..
      కెరీర్ఇంకామొదలవ్వలేదు, ఇప్పుడెందుకు?
    5. Agenda
      The hype – stats
      Industry definitions
      History – a review of computing
      Issues that matter
      Origin
      Grid vs Cloud
      Details
    6. The hype
      Cluster Computing
      Cloud Computing
      Grid Computing 
    7. The hype
    8. Some Definitions
    10. definitions
    11. .. Moving computing and data away from the desktop and the portable PC and simply displaying the results of computing that takes place in a centralized location and is then transmitted via the internet on the user's screen ..
      - John Makroff
    12. .. a computing paradigm shift where computing is moved away from personal computers or an individual application server to a "cloud" of computers ..
      - Wikipedia
    13. .. the idea of relayin on Web-based applications and storing data in the "cloud" of the internet
      - MIT Technology Review
    14. .. it starts with the premise that the data services and architecture should be on servers, We call it cloud computing - they should be in a 'cloud' somewhere..
      - Eric Schmidt
    15. Some other ..
      • Common, Location-independent, Online Utility on Demand*
      • Common implies multi-tenancy, not single or isolated tenancy
      • Utility implies pay-for-use pricing
      • onDemand implies ~infinite, ~immediate, ~invisible scalability
      • Alternatively, a “Zero-One-Infinity” definition:**
      0On-premise infrastructure Acquisition cost Adoption cost Support cost
      1Coherent and resilient environment – not a brittle “software stack”
      Scalability in response to changing needIntegratability/Interoperability with legacy assets and other services Customizability/Programmability from data, through logic, up into the user interface without compromising robust multi-tenancy
      * Joe Weinman, Vice President of Solutions Sales, AT&T, 3 Nov. 2008
      ** From The Jargon File: “Allow none of foo, one of foo, or any number of foo”
    16. .. the trend towards online services that run in a web browser and store users information in a provider's data center ..
      - చక్రవర్తి
    17. location
    18. location
      computations & data are not in the place they used to be in..
    19. location
      why does it matter? a bunch of geeky stuff..
    20. possession implies control
      control implies power
    21. history
      of computing, how is changed
    22. distributed central
    23. history of evolution of computing
    28. SUN 3 workstation
    29. Distributed
      Rich user Interface
      User Autonomy
      Centralized
      Low Cost
      Expert Management
    30. Client
      Client
      Client
      Server
      Client Server – 80s & 90s
      Client
    31. Server
      Client
    32. Server
      Client
    34. ASP.NET
      JavaScript
      XML
      C#
      HTML
      SQL
      Data Store
      Intermediary Application – Cloud Implementation Strategy
    35. enterprise impact
    36. Cultural Challenges
    37. Data
      Integration is hard
      Expensive
      Infrastructure
    38. Data Integration
      Adds meaning
    39. Data Integration is hard
      InvisibleHard to quantify
       Discounted
    40. Financial & Logistics Challenges
    41. Cost v. Benefit
      Time (Cost v. Benefit)
    42. Traditional Software Purchase
      Purchase software
      Purchase hardware
      Create migration plan
      Configure systems
      Configure networks
      Find space in data center
      Setup development & test
      Configure databases
      More…
    43. The Easy Way
      Get a login
    44. Data Integration is hard
      Costs don’t match benefits
    45. How do we make integration easier, and deliver benefits more quickly?
    46. Define Cloud Computing
    47. How do we make integration easier, and deliver benefits more quickly?
      Cloud computing is a way to make integration easier, and deliver benefits more quickly
    48. integration^
      Turn a commodity into a utility
      Necessary, but not differentiating
    49. Not everything’s a commodity
    50. Web Server Farms. Commodity.
    51. Much Enterprise Software. Commodity
    52. Email. A commodity.
    53. Messaging. Maybe not a commodity.
    54. What if… we just gave IT a platform to create their own data models, interfaces, and processes on a dynamic infrastructure [that met corporate requirements] & simply existed as needed?
    55. Results in elevated IT relevance
    56. Other Results…
      Focus on integration will evolve to a more disciplined approach
      Match expenses to benefits
      Enable new classes of applications
    57. Best Practices
    58. Mediation. A secret weapon.
    59. Service Level Management. Don’t even start with “my piece is working fine!”
    60. Security. It’s not (only) what you think it needs to be.
    61. Build a culture of collaboration.
    62. Example: Google Apps
      Cloud Platform
      (Apps Engine)
      Cloud Services
      (Word Processing)
      Cloud Client
      (Mozilla Firefox)
      Cloud hardware
      (Apps Server)
      Cloud storage
      (BigTable DB)
      BigTable
      Cloud Application
      (Google Docs)
    63. issues that matter
    64. Implications
      possession of data
    65. privacy
      our data is hold by 3rd party
    66. security
      portability and preservation
    67. “possession” of computation
    68. market power
    69. how big is the problem?
    70. location
    71. Understanding Cloud Computing
    72. Origin
      “.. Comes from the early days of the Internet where we drew the network as a cloud… we didn’t care where the messages went… the cloud hid it from us” – Kevin Marks, Google
      First cloud around networking (TCP/IP abstraction)
      Second cloud around documents (WWW data abstraction)
      The emerging cloud abstracts infrastructure complexities of servers, applications, data, and heterogeneous platforms
      (“muck” as Amazon’s CEO Jeff Bezos calls it)
    73. 3 Cloud Service Models
      Cloud Software as a Service (SaaS)
      Use provider’s applications over a network
      Cloud Platform as a Service (PaaS)
      Deploy customer-created applications to a cloud
      Cloud Infrastructure as a Service (IaaS)
      Rent processing, storage, network capacity, and other fundamental computing resources
      To be considered “cloud” they must be deployed on top of cloud infrastructure that has the key characteristics
    74. Service Model Architectures
    75. 4 Cloud Deployment Models
      Private cloud
      enterprise owned or leased
      Community cloud
      shared infrastructure for specific community
      Public cloud
      Sold to the public, mega-scale infrastructure
      Hybrid cloud
      composition of two or more clouds
    76. Common Cloud Characteristics
      Cloud computing often leverages:
      Massive scale
      Virtualization
      Non-stop computing
      Free software
      Geographic distribution
      Service oriented software
      Autonomic computing
      Advanced security technologies
    77. is this GRID Computing?
    79. Clouds aren’t all the same
      • Not every cloud is a “grid”
      • Grids imply dynamic arrival/departure
      • Electrical analogy has limits: CPU cycles aren’t substitutable
      • Most clouds are not “compute clusters”
      • Clusters are typically monocultures: just one type of node
      • Applications may require tuning to a particular cluster size
      • Some clouds are servers in virtual slices
      • Virtualized servers can be quickly provisioned
      • Spin-up of instances = new management task
      • Hardware gets cheaper, management…not so much
      • Enterprise cloud computing implies API leverage
      • Immediate focus on function; immediate delivery of value
      • Using appropriate frameworks enables a huge head start
    80. Single-Tenant (vs) Multi-Tenant Architecture
      Shared infrastructure
      Other apps
      App 1
      App 2
      App 3
      App Server
      App Server
      App Server
      Database
      Database
      Database
      OS
      OS
      OS
      Server
      Server
      Server
      Storage
      Storage
      Storage
      Network
      Network
      Network
      Single tenancy gives each customer a dedicated software stack – and each layer in each stack still requires configuration, monitoring, upgrades, security updates, patches, tuning and disaster recovery.
      On a multi-tenant platform, all applications run in a single logical environment: faster, more secure, more available, automatically upgraded and maintained. Any improvement appears to all customers at once.
    81. User Interface
      Logic
      Database
      The technical part : Why multi-tenant matters
      Build strategic applications
      Customize any aspect
      Upgrade when convenient
      Retain IP ownership
      Your Clicks
      Your Code
      Metadata representations:
      Partitioned data, logic and customizations for multiple customers
      Coherent Code Base and Managed Infrastructure
    82. PaaSTaxonamy : Proliferating Platforms
      PaaS for theInquiring Developer
      “Servers as a Service”
      PaaS as anApplication Framework
      UI as a Service
      Virtual Servers
      Virtual Servers
      Virtual Servers
      Logic as a Service
      Virtual Servers
      Virtual Servers
      Integration as a Service
      Python App Server
      Database as a Service
      Database as a Service
      Database as a Service
      Infrastructure as a Service
      Infrastructure as a Service
      Infrastructure as a Service
      ~Familiar Developer Model
      Rapid Scalability
       Offering
      Innovative Technology
      Supports Large-Scale SaaS
      Deep-Dyed Multitenancy
    84. Thank you
    SlideShare Zeitgeist 2009

    + DSK ChakravarthyDSK Chakravarthy Nominate

    custom

    473 views, 2 favs, 0 embeds more stats

    This is a breif demonstration about Cloud Computing more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 473
      • 473 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 2
    • Downloads 100
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Tags

    -->
    What's New

    © 2009 SlideShare Inc. All rights reserved.