Cloud Computing. Aditya Wikan Mahastama

Cloud Computing

Latar Belakang

Sumber: http://perspectives.mvdirona.com/2008/11/28/CostOfPowerInLargeScaleDataCenters.aspx

Kemudian

Fixed costs in capital equipment: Build a server,

Build a system software, Build other infrastructures

Traditional Cost Model

Cloud Cost Model Perusahaan

Perusahaan

Penyedia jasa

Mulai muncul penyedia jasa cloud Internet berkembang

Perusahaan mendukung, karena dapat menghemat biaya, dan dapat diakses lewat internet

The upcoming trend

What Is Cloud Computing?

A virtualised computing power and storage

delivered via platform-agnostic infrastructures of

abstracted hardware and software accessed

over the Internet.

These shared, on-demand IT resources, are created and disposed of efficiently, are dynamically scalable

through a variety of

programmatic interfaces and are billed variably based on measurable usage.

Wait, Cloud dan Grid?

● Grid Computing:

It is made of the virtual computing cluster by using the un-used resources (CPU resources & Disk Storage) from a large number of heterogeneous computers (usually called Desktops), and it provides a structure for solving

massive computing problems. Grid Computing focuses on the

abilities of cross-domain computing support. With Parallel Computing applied, it focuses on the full-use of resources between and

across the companies to jointly solve the tough computing tasks 。

● Cloud Computing:

It is a kind of dynamically scalable computing. The basic concept is to divide the task of computing into several processes. After they are processed and analyzed by the servo group (cloud hosts) distributed over the Internet, the outcomes will be returned to the end-users. Although Cloud Computing

originates from Parallel Computing, it is not away from the concepts of Grid

Computing. But, Cloud Computing focuses more on the

Contoh cloud computing yang

sering kita gunakan:

Why Cloud is Interesting to Businesses

Deploy infrastructures with an API

● No infrastructure hassle ● Any time, anywhere

● Remote access

Less risk

● Nothing to buy

● Change instantly, even OS ● Cancel immediately

● A “throw it out” service

Reliable

● Enterprise-grade hardware ● Automatic replacement

available

● Can use multiple clouds ● Up-to-date software

Tipe Cloud Computing

●

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 mixed

together on the cloud’s servers, storage

systems, and networks.

Examples of a public cloud: Amazon Web

Services and Google's AppEngine

Tipe Cloud Computing

●

A private cloud

is basically an organization that

needs more control over their data than they can

get by using a vendor hosted service

●

A hybrid cloud

combine both public and private

Komponen Arsitektur Cloud

Computing

●

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 user interface such as a web browser.

●

The back end - is the ‘cloud’ itself, comprising

of various computers, servers and data storage

devices.

Komponen Arsitektur Cloud

Computing

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 “pay per use” service: Data Center, Bandwidth, Private Line Access, Servers and Server Room, Firewall,

Storage space etc.

● Examples:

– Amazon ： EC2 (ElasticComputeCloud)

Infrastructure as a Service (IaaS)

● 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

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 that allow users to create and host powerful business

applications, web sites, and mobile apps.

● Examples

– Sales force http://www.force.com

Platform as a Service (PaaS)

●

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

●

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 customer's own computers and simplifying maintenance and support.

● Some of these Web-based applications are free such

as Hotmail, Google Apps, Skype, and many 2.0

applications, while most business-oriented SaaS, such as Sales Force, is leased on a subscription basis

Software as a Service (SaaS)

Five Key Ideas of SaaS:

1. Services are fully managed and hosted

2. Have regular recurring payments (Pay-As-They-Go and Pay-As-They-Grow)

3. Allow for anytime, anywhere access (usually24/7 services)

4. Have multiple tenants on servers

5. Don’t require installation of specialised software

Advantage and disadvantage:

● Advantages: Free, Easy, Consumer Adoption

● Disadvantages: Limited functionality, no control or access to

Cloud Taxonomy

Future Cloud Usage

Health Monitoring

Cloud Computing 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? How does this cost model look over time?

● Legal and organizational issues –What organizational and

legal issues do we need to consider? Are we dealing with patron data? 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?