From  http://geekandpoke.typepad.com
Cloud computing Some material adapted from slides by Indranil Gupta, Jimmy Lim, Christophe Bisciglia, Aaron Kimball, & Sie...
<ul><li>Cloud computing </li></ul><ul><li>The three-tier architectural style & Google AppEngine </li></ul>
Google App Engine (April 2008) Microsoft Azure (Oct 2008) Facebook Platform (May 2007) Amazon EC2 (August 2006) Amazon S3 ...
* From  http://en.wikipedia.org/wiki/Hype_cycle   Cloud Computing
What is Cloud Computing?
Source: http://www.free-pictures-photos.com/
A crisis of complexity.  The need for progress is clear. Steady CAPEX spend Global Annual Server Spending  (IDC) Source: I...
<ul><li>A   new consumption and delivery model  inspired by consumer Internet services. </li></ul><ul><ul><li>Private, Pub...
Is cloud computing really new?  Yes, and no. <ul><li>Cloud computing is a  new consumption  and delivery model  inspired b...
<ul><li>A  new consumption and delivery model  inspired by consumer Internet services. </li></ul><ul><ul><li>Private, Publ...
Key Technology: Virtualization Hardware Operating System App App App Traditional Stack Hardware OS App App App Hypervisor ...
Enterprise Today there are three primary delivery models that companies are implementing for cloud <ul><li>Public Cloud </...
Different Computing Models <ul><li>Infrastructure as a service (IaaS) </li></ul><ul><ul><li>Utility computing </li></ul></...
Elements that Drive Cloud Efficiency and Economics Virtualized environments only get benefits of scale if they are highly ...
Enterprise Benefits from Cloud Computing Legacy environments Cloud enabled enterprise Cloud accelerates business value  ac...
The skeptics
<ul><li>“ Cloud computing is simply a buzzword used to repackage grid computing and utility computing, both of which have ...
<ul><li>“ The interesting thing about cloud computing is that we’ve redefined cloud computing to include everything that w...
 
<ul><li>Marc Benioff , head of  salesforce.com </li></ul><ul><ul><li>“ Cloud computing isn't just candyfloss thinking – it...
<ul><li>John Chambers , Cisco Systems’ CEO </li></ul><ul><ul><li>&quot;a security nightmare.” </li></ul></ul>
&quot;push factors&quot;  for  and &quot;barriers&quot;  against  cloud adoption for each workload type  Push factors <ul>...
<ul><ul><li>Trade-off is value vs. risk of migration </li></ul></ul><ul><ul><li>Workload characteristics are critical   </...
From  http://geekandpoke.typepad.com
Grid vs. Cloud computing (A Grid computing example)
Three-tier architectures and Google AppEngine
Levels of abstraction <ul><li>Different levels of abstraction </li></ul><ul><ul><li>Instruction Set VM: Amazon EC2 </li></...
Traditional WebApplications:  N-Tier Style  <ul><li>Separation of concerns:  Presentation, business and data handling logi...
 
Web Applications with Google AppEngine  Hosting  Server BigTable (your) Java / Python hosted application /  Presentation L...
Why use Google AppEngine? <ul><li>Simplified (Web Application) development  </li></ul><ul><ul><li>(through part of the app...
Why use Google AppEngine? <ul><li>Simplified (Web Application) development  </li></ul><ul><ul><li>Implementation  </li></u...
Adoption  (May 2009) <ul><li>over 80K applications </li></ul><ul><li>serving over 140M pageviews per day </li></ul><ul><li...
A view behind the curtains …
A view behind the curtains …
<ul><li>3-tiered applications engineered for scale and reliability .. </li></ul><ul><ul><li>Slides  </li></ul></ul>
<ul><li>Life of an App Engine Request </li></ul>
 
<ul><li>Differentiate between requests for static and dynamic content. </li></ul>
Request for static content
Request for static content
<ul><li>Defining static content  </li></ul>Request for static content
Request for dynamic content
<ul><li>Defining static content  </li></ul>Request for dynamic content
<ul><li>Defining static content  </li></ul>Request for dynamic content The AppServer
AppServers <ul><li>Runs your code (e.g., servlet) </li></ul><ul><ul><li>Restricted JVM environment </li></ul></ul><ul><ul>...
Requests accessing APIs <ul><li>Use APIs to do things you don't want to do in your runtime, such as... </li></ul><ul><li>C...
Persistency  <ul><li>Across requests </li></ul><ul><ul><li>Session   </li></ul></ul><ul><ul><li>Memcache </li></ul></ul><u...
The AppEngine Datastore <ul><li>Based on BigTable </li></ul><ul><ul><li>http://labs.google.com/papers/bigtable.html   </li...
<ul><ul><li>Benefits </li></ul></ul><ul><ul><ul><li>No machines to manage or count </li></ul></ul></ul><ul><ul><ul><li>Int...
 
To remember <ul><li>AppEngine: specialized platform for Web Applications </li></ul><ul><ul><li>unfit for general computing...
Upcoming SlideShare
Loading in...5
×

s07-08

369

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
369
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
26
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • To start, I don’t think anyone at this point misses the fact that we are at in inflection point with regard to enterprise IT. This crisis of IT complexity and inefficiency is clear, but the issue has become even more pointed in the context of a global economic crisis. This has caused clients to take a hard look at challenges growing within their IT infrastructure. This chart depicts server infrastructure and related operating costs. You can see that OPEX – including management and energy costs – is 70% of the cost of these environments and growing. But this is only one dimension of the issue. When you look at network complexity, or that we have 50% compounded data growth per year – or rapid growth in applications -- this model is not just un-economic but unsustainable In distributed computing environments, up to 85% of computing capacity sits idle. Consumer product and retail industries lose about $40 billion annually, or 3.5 percent of their sales, due to supply chain inefficiencies. 70% on average is spent on maintaining current IT infrastructures versus adding new capabilities. Explosion of information: 54% growth in storage shipments every year. 33% of consumers notified of a security breach will terminate their relationship with the company they perceive as responsible.
  • Cloud computing is one answer to this crisis of complexity in the data center (caused by a Smarter Planet). The consumer Internet is arguably the biggest infrastructure in operation today and so it is not surprising, that consumer Internet services or consumer clouds, are informing the next generation of enterprise IT delivery. We think of clouds primarily as a new way of consuming and delivering IT-enabled services. Many of us use them every day – when we upload our pictures on the Internet for sharing or we download maps for our GPS devices etc. We are not even aware of infrastructure or location. As we translate this approach to the enterprise, we think three aspects of the cloud model are particularly compelling: Self-service – a new relationship with IT, which enables the user a degree of freedom in configuring and accessing services and can dramatically reduce labor on the delivery side. Flexible sourcing options - the idea of more choices and, a hybrid modes of delivery that allows CIOs to optimize costs and qualities of service by work load And much greater focus on scale – that enables both new economics and new capabilities . Most people think about “self-service” from the user and user interface perspective. But more interesting to the delivery team is the process standardization behind it…the way we enable the user interaction with a process that used to be served up by a person. This person was someone with control of the process – access, quality of service and client satisfaction. But we know from a delivery perspective that this model changes a lot more then the interface. It drives the need for a new level of discipline, codification of processes and standardization of the back-office. Think of the ATM in banking….it started as cash dispensing function. This drove a level of internal standardization, but as networks got connected, it forced standards for networking and security across the industry when you want to access money from one back through the ATM of another. In fact, it became a platform for a whole host of retail transactions. We know that IT represents a broad, complex set of functions and is vastly more complex and siloed. As a result, this evolution is equally complex. But the opportunity is to drive operational efficiency and improve service quality and satisfaction.. The second key area is sourcing. The cloud model provides a set of new options. We have been there before – if Intranets and Extranets were about exploiting Internet technology for content, clouds are about computing infrastructure and services. There are criteria that inform where you compute and how you use the delivery options – Security, control, level of flexibility etc. One aspect that is often underestimated is the advantage in ‘time-to-market’ – a ‘ready-to-use’ service that can be plugged into an existing infrastructure, seamlessly for the user can be a great option for timing and lower risk. There are many considerations, but none is more important then the role of the IT organization and managing IT services on both sides of this boundary. We know from experience the cost of letting new technologies and paradigms run wild in the enterprise. The management system and governance of this hybrid infrastructure will be critical to successfully integrating a cloud in the enterprise.
  • Cloud computing is one answer to this crisis of complexity in the data center (caused by a Smarter Planet). The consumer Internet is arguably the biggest infrastructure in operation today and so it is not surprising, that consumer Internet services or consumer clouds, are informing the next generation of enterprise IT delivery. We think of clouds primarily as a new way of consuming and delivering IT-enabled services. Many of us use them every day – when we upload our pictures on the Internet for sharing or we download maps for our GPS devices etc. We are not even aware of infrastructure or location. As we translate this approach to the enterprise, we think three aspects of the cloud model are particularly compelling: Self-service – a new relationship with IT, which enables the user a degree of freedom in configuring and accessing services and can dramatically reduce labor on the delivery side. Flexible sourcing options - the idea of more choices and, a hybrid modes of delivery that allows CIOs to optimize costs and qualities of service by work load And much greater focus on scale – that enables both new economics and new capabilities . Most people think about “self-service” from the user and user interface perspective. But more interesting to the delivery team is the process standardization behind it…the way we enable the user interaction with a process that used to be served up by a person. This person was someone with control of the process – access, quality of service and client satisfaction. But we know from a delivery perspective that this model changes a lot more then the interface. It drives the need for a new level of discipline, codification of processes and standardization of the back-office. Think of the ATM in banking….it started as cash dispensing function. This drove a level of internal standardization, but as networks got connected, it forced standards for networking and security across the industry when you want to access money from one back through the ATM of another. In fact, it became a platform for a whole host of retail transactions. We know that IT represents a broad, complex set of functions and is vastly more complex and siloed. As a result, this evolution is equally complex. But the opportunity is to drive operational efficiency and improve service quality and satisfaction.. The second key area is sourcing. The cloud model provides a set of new options. We have been there before – if Intranets and Extranets were about exploiting Internet technology for content, clouds are about computing infrastructure and services. There are criteria that inform where you compute and how you use the delivery options – Security, control, level of flexibility etc. One aspect that is often underestimated is the advantage in ‘time-to-market’ – a ‘ready-to-use’ service that can be plugged into an existing infrastructure, seamlessly for the user can be a great option for timing and lower risk. There are many considerations, but none is more important then the role of the IT organization and managing IT services on both sides of this boundary. We know from experience the cost of letting new technologies and paradigms run wild in the enterprise. The management system and governance of this hybrid infrastructure will be critical to successfully integrating a cloud in the enterprise.
  • This is not just cloud washing. This is really a different consumption model….
  • 3 ti
  • s07-08

    1. 1. From http://geekandpoke.typepad.com
    2. 2. Cloud computing Some material adapted from slides by Indranil Gupta, Jimmy Lim, Christophe Bisciglia, Aaron Kimball, & Sierra Michels-Slettvet, Google Distributed Computing Seminar, 2007 (licensed under Creation Commons Attribution 3.0 License)
    3. 3. <ul><li>Cloud computing </li></ul><ul><li>The three-tier architectural style & Google AppEngine </li></ul>
    4. 4. Google App Engine (April 2008) Microsoft Azure (Oct 2008) Facebook Platform (May 2007) Amazon EC2 (August 2006) Amazon S3 (March 2006) Salesforce AppExchange (March 2006) Grid computing Virtualization Cloud computing
    5. 5.
    6. 6. * From http://en.wikipedia.org/wiki/Hype_cycle Cloud Computing
    7. 7.
    8. 8. What is Cloud Computing?
    9. 9. Source: http://www.free-pictures-photos.com/
    10. 10. A crisis of complexity. The need for progress is clear. Steady CAPEX spend Global Annual Server Spending (IDC) Source: IBM Corporate Strategy analysis of IDC data Uncontrolled management and energy costs To make progress, delivery organizations must address the server, storage and network operating cost problem, not just CAPEX $0B 50 100 150 200 250 300 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 New system spend Management and admin costs Power and cooling costs
    11. 11. <ul><li>A new consumption and delivery model inspired by consumer Internet services. </li></ul><ul><ul><li>Private, Public and Hybrid </li></ul></ul><ul><ul><li>Workload and/or Programming Model Specific </li></ul></ul><ul><ul><li>The Industrialization of Delivery for IT supported Services </li></ul></ul>Cloud Services Cloud Computing Model <ul><ul><li>Self-service </li></ul></ul><ul><ul><li>Sourcing options </li></ul></ul><ul><ul><li>Economies-of-scale </li></ul></ul>Multiple Types of Clouds will co-exist: “ Cloud” represents: Cloud enables: “ Cloud” is:
    12. 12. Is cloud computing really new? Yes, and no. <ul><li>Cloud computing is a new consumption and delivery model inspired by consumer Internet services. Cloud computing exhibits the following 5 key characteristics: </li></ul><ul><ul><li>On-demand self-service </li></ul></ul><ul><ul><li>Ubiquitous network access </li></ul></ul><ul><ul><li>Location independent resource pooling </li></ul></ul><ul><ul><li>Rapid elasticity </li></ul></ul><ul><ul><li>Pay per use </li></ul></ul><ul><li>While the technology is not new, the end user focus of self-service, self-management leveraging these technologies is new. </li></ul>Business Services IT Services Virtualization Service Automation & SOA Usage Tracking Web 2.0 End User Focused
    13. 13. <ul><li>A new consumption and delivery model inspired by consumer Internet services. </li></ul><ul><ul><li>Private, Public and Hybrid </li></ul></ul><ul><ul><li>Workload and/or Programming Model Specific </li></ul></ul><ul><ul><li>The Industrialization of Delivery for IT supported Services </li></ul></ul>Cloud Services Cloud Computing Model <ul><ul><li>Self-service </li></ul></ul><ul><ul><li>Sourcing options </li></ul></ul><ul><ul><li>Economies-of-scale </li></ul></ul>Multiple Types of Clouds will co-exist: “ Cloud” represents: Cloud enables: “ Cloud” is:
    14. 14. Key Technology: Virtualization Hardware Operating System App App App Traditional Stack Hardware OS App App App Hypervisor OS OS Virtualized Stack Hardware JVM App App App OS/JVM Managent JVM JVM Virtualized Stack
    15. 15. Enterprise Today there are three primary delivery models that companies are implementing for cloud <ul><li>Public Cloud </li></ul><ul><li>IT activities/functions are provided “as a service,” over the Internet </li></ul><ul><li>Key features: </li></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Automatic/rapid provisioning </li></ul></ul><ul><ul><li>Standardized offerings </li></ul></ul><ul><ul><li>Consumption-based pricing. </li></ul></ul><ul><ul><li>Multi-tenancy </li></ul></ul>Traditional Enterprise IT <ul><li>Private Cloud </li></ul><ul><li>IT activities/functions are provided “as a service,” over an intranet, within the enterprise and behind the firewall </li></ul><ul><li>Key features include: </li></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Automatic/rapid provisioning </li></ul></ul><ul><ul><li>Chargeback ability </li></ul></ul><ul><ul><li>Widespread virtualization </li></ul></ul>Private Cloud Public Clouds Hybrid Cloud Source: IBM Market Insights, Cloud Computing Research , July 2009.
    16. 16. Different Computing Models <ul><li>Infrastructure as a service (IaaS) </li></ul><ul><ul><li>Utility computing </li></ul></ul><ul><ul><li>Why buy machines when you can rent cycles? </li></ul></ul><ul><ul><li>Examples: Amazon’s EC2, GoGrid, AppNexus </li></ul></ul><ul><li>Platform as a Service (PaaS) </li></ul><ul><ul><li>Give me nice API and take care of the implementation </li></ul></ul><ul><ul><li>Example: Google App Engine </li></ul></ul><ul><li>Software as a Service (SaaS) </li></ul><ul><ul><li>Just run it for me! </li></ul></ul><ul><ul><li>Example: Gmail </li></ul></ul>
    17. 17. Elements that Drive Cloud Efficiency and Economics Virtualized environments only get benefits of scale if they are highly utilized Drives lower capital requirements More complexity = less automation possible = people needed Take repeatable tasks and automate Labor Leverage Infrastructure Leverage Clients who can “serve themselves” require less support and get services Self Service Automation of Management Standardization of Workloads Virtualization of Hardware Utilization of Infrastructure
    18. 18. Enterprise Benefits from Cloud Computing Legacy environments Cloud enabled enterprise Cloud accelerates business value across a wide variety of domains. Capability From To None Self service Fixed cost model Metering/Billing Weeks Test Provisioning Payback period for new services Release Management Change Management Server/Storage Utilization Years Weeks Months 10-20% Unlimited Granular Minutes Months Minutes Days/Hours 70-90%
    19. 19. The skeptics
    20. 20. <ul><li>“ Cloud computing is simply a buzzword used to repackage grid computing and utility computing, both of which have existed for decades.” </li></ul>whatis.com Definition of Cloud Computing
    21. 21. <ul><li>“ The interesting thing about cloud computing is that we’ve redefined cloud computing to include everything that we already do. […] </li></ul><ul><li>The computer industry is the only industry that is more fashion-driven than women’s fashion. </li></ul><ul><li>Maybe I’m an idiot, but I have no idea what anyone is talking about. What is it? It’s complete gibberish. It’s insane. When is this idiocy going to stop?” </li></ul>Larry Ellison During Oracle’s Analyst Day From http://blogs.wsj.com/biztech/2008/09/25/larry-ellisons-brilliant-anti-cloud-computing-rant/
    22. 23. <ul><li>Marc Benioff , head of salesforce.com </li></ul><ul><ul><li>“ Cloud computing isn't just candyfloss thinking – it's the future . If it isn't, I don't know what is. We're in it. You're going to see this model dominate our industry.&quot; </li></ul></ul><ul><ul><li>Is data really safe in the cloud? &quot;All complex systems have planned and unplanned downtime. The reality is we are able to provide higher levels of reliability and availability than most companies could provide on their own, &quot; says Benioff </li></ul></ul>
    23. 24. <ul><li>John Chambers , Cisco Systems’ CEO </li></ul><ul><ul><li>&quot;a security nightmare.” </li></ul></ul>
    24. 25. &quot;push factors&quot; for and &quot;barriers&quot; against cloud adoption for each workload type Push factors <ul><li>Fluctuating demand </li></ul><ul><li>Highly standardized applications </li></ul><ul><li>Modular, independent applications </li></ul><ul><li>Unacceptably high costs </li></ul>Barriers <ul><li>Data privacy or regulatory and compliance issues </li></ul><ul><li>High level of Internal control required </li></ul><ul><li>Accessibility and reliability are a concern </li></ul><ul><li>Cost is not a concern </li></ul>Source: IBM Market Insights, Cloud Computing Research , July 2009. n=1,090
    25. 26. <ul><ul><li>Trade-off is value vs. risk of migration </li></ul></ul><ul><ul><li>Workload characteristics are critical </li></ul></ul><ul><ul><li>New workloads will emerge as cloud makes them affordable (eg pervasive analytics, Smart Healthcare) </li></ul></ul>
    26. 27. From http://geekandpoke.typepad.com
    27. 28. Grid vs. Cloud computing (A Grid computing example)
    28. 29. Three-tier architectures and Google AppEngine
    29. 30. Levels of abstraction <ul><li>Different levels of abstraction </li></ul><ul><ul><li>Instruction Set VM: Amazon EC2 </li></ul></ul><ul><ul><li>ApplicationLevel VM: Google AppEngine </li></ul></ul><ul><li>Similar to languages </li></ul><ul><ul><li>Higher level abstractions can be built on top of lower ones </li></ul></ul>EC2 Azure AppEngine Force.com Lower-level, More flexibility, More management Not scalable by default Higher-level, Less flexibility, Less management Automatically scalable
    30. 31. Traditional WebApplications: N-Tier Style <ul><li>Separation of concerns: Presentation, business and data handling logic are clearly partitioned in different tiers. </li></ul><ul><li>Synchronous communications: Communications between tiers is synchronous request-reply. Each tier waits for a response from the other tier before proceeding. </li></ul><ul><li>Flexible deployment: There are no restrictions on how a multi-tier application is deployed. All tiers could run on the same machine, or each tier may be deployed on its own machine. </li></ul>Databases Application Logic Web Server / Presentation Logic Web Client Web Client Web Client Client Tier Web Server Tier Business Logic Tier Data Management Tier
    31. 33. Web Applications with Google AppEngine Hosting Server BigTable (your) Java / Python hosted application / Presentation Logic Web Client Web Client Web Client Client Tier Web Server Tier Business Logic Tier Data Management Tier
    32. 34. Why use Google AppEngine? <ul><li>Simplified (Web Application) development </li></ul><ul><ul><li>(through part of the application lifecycle) </li></ul></ul><ul><ul><li>by leveraging Google infrastructure </li></ul></ul><ul><ul><ul><li>Scalability </li></ul></ul></ul><ul><ul><ul><li>Reliability </li></ul></ul></ul><ul><ul><ul><li>Functionality </li></ul></ul></ul>
    33. 35. Why use Google AppEngine? <ul><li>Simplified (Web Application) development </li></ul><ul><ul><li>Implementation </li></ul></ul><ul><ul><ul><li>Simplified/integrated application monitoring and logging </li></ul></ul></ul><ul><ul><ul><li>Simplified user authentication </li></ul></ul></ul><ul><ul><ul><li>Tooling </li></ul></ul></ul><ul><ul><li>Deployment / maintenance / and use </li></ul></ul><ul><ul><ul><li>No servers to setup – Apache, EJB containers, database </li></ul></ul></ul><ul><ul><ul><li>No server management / monitoring / upgrade </li></ul></ul></ul><ul><ul><ul><li>Billing model: Pay per use </li></ul></ul></ul><ul><ul><ul><ul><li>Reduced upfront investment </li></ul></ul></ul></ul><ul><ul><ul><li>[Promise of] scalability </li></ul></ul></ul><ul><ul><ul><li>Monitoring and statistics </li></ul></ul></ul><ul><ul><ul><li>User authentication </li></ul></ul></ul>
    34. 36. Adoption (May 2009) <ul><li>over 80K applications </li></ul><ul><li>serving over 140M pageviews per day </li></ul><ul><li>over 200K developers </li></ul><ul><li>rwo supported languages: Python and Java </li></ul>
    35. 37. A view behind the curtains …
    36. 38. A view behind the curtains …
    37. 39. <ul><li>3-tiered applications engineered for scale and reliability .. </li></ul><ul><ul><li>Slides </li></ul></ul>
    38. 40. <ul><li>Life of an App Engine Request </li></ul>
    39. 42. <ul><li>Differentiate between requests for static and dynamic content. </li></ul>
    40. 43. Request for static content
    41. 44. Request for static content
    42. 45. <ul><li>Defining static content </li></ul>Request for static content
    43. 46. Request for dynamic content
    44. 47. <ul><li>Defining static content </li></ul>Request for dynamic content
    45. 48. <ul><li>Defining static content </li></ul>Request for dynamic content The AppServer
    46. 49. AppServers <ul><li>Runs your code (e.g., servlet) </li></ul><ul><ul><li>Restricted JVM environment </li></ul></ul><ul><ul><ul><li>Threads, security manager, file-access read only, new connections, reflection </li></ul></ul></ul><ul><li>Enforces Isolation </li></ul><ul><ul><li>Keeps apps safe from each other </li></ul></ul><ul><li>Many applications, many concurrent requests </li></ul><ul><ul><li>Smaller footprint </li></ul></ul><ul><li>Stateless! </li></ul><ul><ul><li>Allows for scheduling flexibility </li></ul></ul><ul><li>Time bound! </li></ul><ul><li>Service API requests to access to other services </li></ul>
    47. 50. Requests accessing APIs <ul><li>Use APIs to do things you don't want to do in your runtime, such as... </li></ul><ul><li>Calls are blocking! </li></ul>
    48. 51. Persistency <ul><li>Across requests </li></ul><ul><ul><li>Session </li></ul></ul><ul><ul><li>Memcache </li></ul></ul><ul><ul><li>Datastore </li></ul></ul>
    49. 52. The AppEngine Datastore <ul><li>Based on BigTable </li></ul><ul><ul><li>http://labs.google.com/papers/bigtable.html </li></ul></ul><ul><li>Replicated and fault tolerant </li></ul><ul><ul><li>On commit: ≥3 machines </li></ul></ul><ul><ul><li>Geographically distributed </li></ul></ul><ul><li>No relational model! </li></ul><ul><li>New API. </li></ul>
    50. 53. <ul><ul><li>Benefits </li></ul></ul><ul><ul><ul><li>No machines to manage or count </li></ul></ul></ul><ul><ul><ul><li>Integrated development/production environment </li></ul></ul></ul><ul><ul><ul><ul><li>Use Google tools (e.g., Admin Console_ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Scalable logging and aggregation mechanisms </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Easy deployment </li></ul></ul></ul></ul><ul><ul><li>Some restrictions </li></ul></ul><ul><ul><ul><li>Small request footprint (implicit) </li></ul></ul></ul><ul><ul><ul><li>Fast requests </li></ul></ul></ul><ul><ul><ul><li>Stateless requests </li></ul></ul></ul><ul><ul><ul><li>Schemaless data model </li></ul></ul></ul><ul><ul><ul><li>[understand their impact and the reasons they were added] </li></ul></ul></ul>
    51. 55. To remember <ul><li>AppEngine: specialized platform for Web Applications </li></ul><ul><ul><li>unfit for general computing. </li></ul></ul><ul><li>Support for part of lifecycle of a web application </li></ul><ul><li>Offers transparent access to scalable infrastructure </li></ul><ul><ul><li>You pay a price for the ‘infinite’ scalability offered: constrains on your application </li></ul></ul><ul><ul><ul><li>stateless requests, schemaless data models, limits on resource usage for each request . </li></ul></ul></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×