ATI – Cloud Computing
Latar belakang: server
Cost model di perusahaan
Traditional cost model
Traditional vs. Cloud application
development
Structural Oriented Programming Object Oriented Programming Service Oriented Architecture Cloud Computing Non Structural Programming Programming Internet Mainframe Client Server InternetTraditional vs. Cloud application
development
Single Tenant Organisation Organisation C Organisation A Organisation B Compile time Application Generation Relational DB Structure-Driven Architecture Dedicated Resources Tradition al Runtime Application Generation Metadata-Driven Architecture On Demand Shared Resources Cloud Infrastructure Application Platform Infrastructure as a Service Application as a Service Platform as a Service Multitenant Resources Multiple Codebases Local Environment Complex Collaboration and Integration No Sharing Constraints and Governance Limits Resources Single Codebase Hosted Simple Collaboration and Integration Sharing Constraints and Governance LimitsCloud Computing is…
… virtualized computing power and storage delivered via platform-agnostic
infrastructures of abstracted hardware and
software, accessed over the Internet. software, accessed over the Internet.
These shared, on-demand IT resources, are
created and disposed efficiently, are
dynamically scalable through a variety of programmatic interfaces and are billed variably based on measurable usage.
What Cloud Computing for?
1. Web-scale problems 2. Large data centers
3. Different models of computing
4. Highly-interactive Web applications 4. Highly-interactive Web applications
1. Web-Scale Problems
• 2 Characteristics:
– Data-intensive focused problem
– Processing-intensive focused problem
• Examples:
• Examples:
– Crawling, indexing, searching, mining the Web
– Artificial Life
How much data?
• Internet archive-Wayback Machine has 2 PB + 20 TB/month (2006)
• Google processes 20 PB a day (2008)
• “all words ever spoken by human beings” ~ 5 EB
• National Oceanic and Atmospheric Administration has
• National Oceanic and Atmospheric Administration has ~1 PB climate data (2007)
• CERN’s LHC (particle accelerator) will generate 15 PB a year (2008)
2. Large Data Centers
• Web-scale problems? throw more machines
at it!
• Trends: centralization of computing resources in large data centers
in large data centers
– Needs more infrastructures!
• Important Issues:
– Redundancy
3. Different Computing Models
• Utility computing
– Why buy machines when you can rent?
– Examples: Amazon’s EC2, GoGrid, AppNexus
• Infrastructure as a Service (IaaS) – network architects
• Platform as a Service (PaaS) - developers
• Software as a Service (SaaS) – end users “Why do it yourself if you can pay someone to do it for you?”
The Cloud Computing Principles
- User centric: berorientasi pada pengguna - Openness: teknologinya standard
- Interoperability: antar platform - Evolution: mudah dikembangkan - Evolution: mudah dikembangkan
- Transparency: tidak perlu mempermasalahkan dimana client dan servernya
Cloud Computing’s Benefits
Software as a Subscription
Reduced Software Maintenance
Cost Reduction
Environmentally Friendly
Matches Current Computing Trends
Portability
Ease of Use
• Deploy infrastructure with a API
– No cabling, screwdrivers, racking, unboxing,
buying
– Anytime, anywhere, anyplace
– Anytime, anywhere, anyplace
Risk
• Nothing to buy
• Cancel immediately
• Change instantly, even operating systems
• Throw it out
• Throw it out
• Rebuild it instantly after testing
Reliability
• Based on enterprise grade hardware
• Design for failures:
– Automatically replacements
– Use multiple clouds
Components of Cloud Computing
Architecture
• the front end - is the part seen by the client, i.e. the computer user.
– This includes the client’s network (or computer)
and the applications used to access the cloud via and the applications used to access the cloud via
user interface such as a web browser.
• the back end - is the ‘cloud’ itself, comprising
various computers, servers and data storage devices.
Cloud computing types
• Public clouds computing environment are
open for use to anyone who wants to sign up and use them.
• These are run by vendors and applications from different customers are likely to be from different customers are likely to be mixed together on the cloud’s servers,
storage systems, and networks.
• Examples of a public cloud: Amazon Web Services
• A private cloud is basically an organization that needs more control over their data than they can get by
using a vendor hosted service
Cloud computing types
• A hybrid cloud combine both public and private cloud models.
Cloud computing architecture
Cloud Service Provider
Security Portal
Cloud Service
Consumers
API Software as a Service Platform as a Service Infrastructure as a Service InfrastructureCloud Service Management
Cloud Computing Operating
Environment Management Cloud Business Management Security Cloud Tools Cloud Application User Legacy System, Infrastructure Local Development Platform & IDE
Cloud Application
Major Players’
Cloud Computing Services
Google Microsoft Force.com Cordys IBM Amazon MOSSO Force.com
Types of Cloud Services
1. IaaS
2. PaaS 3. SaaS
Infrastructure as a Service (IaaS)
• sometimes referred as HaaS or Hardware as a
Service and it involves both storage services and computing power.
• Provides user computing resources and storage
comprised with many servers as an on-demand and
comprised with many servers as an on-demand and
“pay per use” service: Data Center, Bandwidth, Private Line Access, Servers and Server Room, Firewall, Storage space, VPN …..
• Examples:
– Amazon EC2 (ElasticComputeCloud)
Cloud “Infrastructure”
• Provide “Compute” and “Storage” clouds • Virtualization layers (hardware/software)
• Examples: Amazon EC2, GoGrid, Amazon S3, Nirvanix, Linode • Advantages: Full control of environments and infrastructure • Disadvantages: premium price point, limited competition • Disadvantages: premium price point, limited competition
Platform as-a-Service (PaaS)
With PaaS, computing platform provides supplies
tools and a development environment to help
companies build, test, and deploy Web-based applications.
Bundles all stack components (hardware,
infrastructure, storage) together with database, security, workflow, user interface, and other tools infrastructure, storage) together with database, security, workflow, user interface, and other tools
that allow users to create and host powerful business applications, web sites, and mobile apps.
API based, rapid application with low cost
Examples
– Sales force http://www.force.com – Windows Azure
Cloud “Platforms”
• “Closed” environments
• Examples: Google App Engine, Heroku, Mosso, Engine Yard, Joyent or Force.com (SalesForce Dev Platform)
• Advantages: Good for developers, more control than “Application” Clouds, tightly configured
“Application” Clouds, tightly configured
• Disadvantages: Restricted to what is available, other dependencies
Software as a Service (SaaS )
• Applications or software is delivered as a
service to the customer who can access the program from any online device, eliminating
the need to install and run the application on the need to install and run the application on the customer's own computers and simplifying maintenance and support.
• Ex: Hotmail, Google Apps, Skype, Sales Force
SaaS can be defined through five key
ideas:
• Services are fully managed and hosted;
• Have regular recurring payments (Pay-As-They-Go and Pay-As-They-Grow);
• Allow for anytime, anywhere access (usually
• Allow for anytime, anywhere access (usually 24/7 services) ;
• Have multiple tenants on servers
• Don’t require installation of specialized software
Cloud “Applications”
• Most common Cloud / Many providers of different services • Examples: Gmail, Yahoo! Mail, Quicken Online, Skype
• Advantages: Free, Easy, Consumer Adoption
• Disadvantages: Limited functionality, no control or access to underlying technology
Cloud OS & Addition
• EyeOS - http://www.eyeos.com/
• ZeroPC - http://www.zeropc.com/
• Cloud computing is eco-friendly
• Cloud computing is impossible without the Internet
$50 per user per year
Cloud computing and IT issues:
• Service level agreements – What assurances do we have
for uptime, legal protection, and security?
• Uptime and reliability – How does this provider compare
to being able to locally host and manage our resources?
• Cost and affordability – What personnel and technology
resources are involved with a hosted versus local solution?
• Legal and organizational issues
• Legal and organizational issues – What organizational
and legal issues do we need to consider? Are we sure that the platform and our connection to it are secure?
• Staff knowledge – How would migrating to this platform
impact staff knowledge and competency? Do we know everything that we need to know?
