Cloud Computing.pptx

• Also known as on demand computing, it is a
provision of IT resources and service over the
internet.
•Provides the user and organisation to store their
data and process them at 3rd party data centres.
•From a “Business Perspective”,
“Cloud computing is an IT deployment model, based
on virtualisation where resources in terms of
infrastructure, application and data are deployed via
internet as distributed service by one or several
service providers”

• On demand capabilties
• Broad network access
• Resource pooling
• Rapid Elasticity
• Measured Service

•A business will secure cloud-hosting services through a
cloud host provider
•You have access to your services and you have the
power to change cloud services through an online
control panel or directly with the provider.
•You can add or delete users and change storage
networks and software as needed.
•A pay-for-what-you-use scenario.

•Your team can access business management
solutions.
•They can use these devices wherever they are
located with a simple online access point.
• During business hours or on off-times, employees
can stay on top of projects, contracts, and customers
•Broad network access includes private clouds that
operate within a company’s firewall, public clouds, or
a hybrid deployment.

•The cloud enables employees to enter and use data
within the business management software hosted in the
cloud at the same time, from any location, and at any
time.
•Attractive feature for multiple business offices and field
service or sales teams that are usually outside the office.

•If anything, the cloud is flexible and scalable to suit
immediate business needs.
•Quickly and easily add or remove users, software
features, and other resources.

•You only pay for what you use.
•You and your cloud provider can measure storage
levels, processing, bandwidth, and the number of
user accounts and you are billed appropriately.
•The amount of resources that you may use can be
monitored and controlled from both your side and
your cloud provider’s side which provides
transparency.

•Though service-oriented
architecture advocates "everything as
a service" , cloud-computing providers
offer their "services" according to
different models, which happen to
form a stack.
•The different types of service models
are :-
Infrastructure as a
service(IAAS)
Platform as a service(PAAS)
Software as a service(SAAS)

•Most basic cloud service model
•Provides computers physical or virtual machines,
server storage

•Provides development environment to app providers
•The provider typically develops toolkit and standards
for development and channels for distribution and
payment.
•Cloud providers deliver a computing platform,
typically including operating system, programming-
language execution environment, database, and web
server.

•User gains access to application services and
databases.
•Priced on pay per use basis

•In addition to the three basic service models, i.e.
Infrastructure as a service(IAAS), Software as a
Service(SAAS) and Platform as a Service(PAAS),three
more have been recently introduced.
•These include :-
Storage as a Service
Network as a Service
Information as a Service

• The basic components of IaaS include:-
Virtual Machines
Virtual Disk
Geographic Region
Failure-insulated Zone
Archival Storage

•The virtual machine is the basic unit of computing in
the system.
• Virtual machines come are of two types: non-
persistent and persistent.
Non- Persistent Virtual Machines: They do not
persist any data after the machine has been turned
off. Every modification done while the system was
on is lost. Hence everything has to be stored at an
external location(Virtual disks) to be recorded.

Persistent Virtual Machines: A persistent machine is
backed by permanent storage (likely a virtual disk) that
continues to exist after the machine is stopped. This
allows the machine to be restarted into the same state
that it was in the last time it was stopped.

•A virtual disk is size-configurable, permanent, block-level
storage that can be mounted to a running virtual
machine.
•Virtual disks are capable of random I/O.
•Virtual disks can only be mounted to a single virtual
machine at any time, but can be mounted to multiple
machines throughout its lifetime.
•Virtual disks continue to exist (unmounted) even after
the virtual machine they were mounted to has shut
down.

• Both Virtual Machines and Virtual Disks are susceptible to
some hardware failures and disaster scenarios.

•Geographic region is the place where the resources
powering these virtual entities physically reside.
•The distance between your virtual components becomes
important when discussing latency, and disaster situations.
• A large public cloud such as Amazon uses geographic
regions that are thousands of miles apart.

•A smaller private cloud may use geographic regions that
represent servers in buildings that across the street from
each other.
•In general, the farther apart the geographic regions, the
more isolation and latency between them

•Failure-insulated zones are divisions within a
geographic region that are, as much as possible, isolated
from expected localized failures such as disk or power
supply failure.
• A large public cloud may use zones that are located in
rooms separated by thick firewalls (physical ones, not
the networking kind)
• A smaller private cloud may use zones as simple as two
racks that sit beside each other. As with geographic
regions, the more isolation the better.

•Archival storage is long term, permanent, blob-level
storage.
•Archival storage allows the storage and retrieval of
individual blobs, but does not allow random I/O within the
blobs.
•Archival storage is not mounted to any virtual machine,
and can be accessed by multiple virtual machines at the
same time.

•Archival storage exists outside of any specific geographic
region.
• It is considered to be completely durable, but not always
available.

•Cost Effective: Only pay for what you need, when you need
it.
•Easily Scalable: IaaS cloud is good for when you need to
expand or scale back.
•Available Anywhere: An Internet connection is all you
need to access the service from anywhere.
•Maintenance-free: Businesses don’t need to worry about
complexities and expenses of managing underlying
hardware.

•No Single Point of Failure: IaaS can run even if one server
goes down.
•Physical Security: Exclusive datacenters can feature
everything necessary to ensure the absolute best in
uptime and reliability for sites.
•Adaptability: Business can customize processes, platform
configurations, and terms of service.
•Less Strain on IT Departments: Businesses don’t have to
purchase, install, or integrate components themselves.

•Business efficiency and productivity largely depends on the
vendor's capabilities
•Potentially greater long-term cost
•Centralization requires new/ different security measures

• PaaS facilitates the users with an online platform where
they could run their softwares and other services.
•Typical components of PaaS include :-
Elastic Load Balancer
Service Load Monitor
Cloud Controller
Artifacts Distribution Server
Deployment Synchroniser

• It balances load in the cloud or across on-premise cloud
service instances.
• To deal with load characteristics that change dynamically,
the ELB should provide fail-over, multi-tenancy, and auto-
scaling of services.
•They can guide traffic based on the target service or
consuming tenant.

•Elastic Load Balancers are capable of managing traffic
across different topologies and guide traffic according to
cost, resource pooling policies, and performance.
•A Cloud Native Elastic Load Balancer can adjust to
topology changes fast, and is securely integrated with the
Service Load monitor component.

•This component uses multiple sources (such as load
balancers, app servers etc) to acquire load information,
and communicates performance and utilization
information to an ELB
•The ELB is responsible for distributing requests to the
most favorable instances, based on load balancing
policies, tenant association, partitioning policies, and
SLAs.

•Based on the input of Service Load Monitor, this
component creates and removes cloud instances
(Linux containers or virtual machines).
• It makes the instance number satisfy shifting
demands, and matches instance scaling with
quota and reservation thresholds (such as
maximum/minimum instance count).

•It maintains a versioned pool of run-time artifacts and
their connection with cloud service definitions.
•It takes complete applications (i.e. services, application
code, mediation flows, APIs and business rules) and
breaks the combined bundle into per-instance
constituents, which are then loaded into instances using
a Deployment Synchronizer.

•It examines and deploys the right code for each
cloud application platform instance (e.g. Enterprise
Service Bus, application server, API Gateway).
•With the use of a Cloud Native PaaS Management
Console, control of services, tenant partitions,
quality of service, and code deployment by either
command-line tooling or web-based user interface
is made possible.

•Quick testing and deployment:
Development teams can try different configurations,
multiple machines and different locations, to run stress
tests and assess performance, compatibility, and response
in ways that are impossible in a local environment.
With quick testing of applications, deployment too
becomes faster.

•Dynamic allocation:
In today’s competitive market, IT teams need to have
the flexibility to quickly test and put a new feature of
an application or a new service on the market
 Test these on a small section of clients before
making them available to the entire world.
With PaaS and cloud computing, such tasks have
now become possible.

•Increased focus on business and boost to internal
entrepreneurship:
As companies no longer need to expend effort on the
maintenance and choice of systems, they can focus
more on their core business.
Quicker development and deployment of infrastructure
on line is possible, which in turn can empower visionaries
and give internal entrepreneurship a boost.

 By setting aside a specific sum under the cloud
budget, companies can let their IT teams experiment
with cloud computing resources, and see what
innovative ideas they can come up with.

•Data security:
Many companies still have low confidence in the level of
data security offered by PaaS.
Many businesses are still skeptical about having their
applications hosted by a third party, while some
enterprises and government clients need to be assured of
compliance with all applicable regulations concerning
security, privacy, and data retention.

•Limited flexibility:
PaaS solutions can’t match the flexibility of IaaS
(Infrastructure as a Service) offerings.
Unlike their IaaS counterparts, PaaS customers cannot
necessarily create and delete multiple virtual machines
easily.
PaaS falls short as it doesn’t represent a complete
product in the way that SaaS does. So, a company still
needs to put in development effort to design, create, and
test programs before they are deployed for the end users.

•Customer captivity:
With a limited number of PaaS vendors in the market
today, each of which wants to build a binding relationship
through its comprehensive offerings, a vendor lock-in
period is often the norm, which can limit the client’s
choices.
•Problems of integration with in-house systems and
applications:
Integration of PaaS services with the rest of your systems
and applications could trigger an increase in complexity.

• The business components
of SaaS include:
Customer Relationship
Management
Marketing Automation
Billing
Consumer Analytics
Community

•SaaS vendors need a central repository of customers.
•In some cases (especially as the solution is more
consumer oriented), the CRM system is a built-in part
of the application.
•Core CRM functionality includes sales activities
(associating accounts with sales people, forecasting),
though in most cases CRM systems span into adjacent
areas (customer support being a notable one).

•It addresses the need to manage the communication
with prospects and customers, typically over e-mail.
•The goal of these activities is to “nurture” leads and rank
prospects for more efficient use of sales people’s time..

•All SaaS companies have at least some need to bill
customers; or at least, so I would hope.
•The recurring billing space addresses needs such as
associating customers with plans (for billing
purposes), usage-based billing(e.g., storage space,
minutes), as well as the actual collection and
communication (e.g., a “reminder” process
called dunning).

•Popularized by Google Analytics, customer analytics
attempts to help SaaS providers analyze the behavior
of their customers within the application (and
potentially elsewhere).

• An area that may have been referred to
as helpdesk or customer support in the past now includes
core customer support tools (e.g., ZenDesk, TenderApp),
collaborative product ideas (e.g., UserVoice,
GetSatisfaction), feedback forms (Kampyle), live chat
(ClickDesk, Kayako, LivePerson), as well as traditional
knowledge-base tools and self-learning ones (e.g.,
NanoRep).
•To build a strong community of users and provide them
with superb support, more than one tool may be required.

•High Adoption
SaaS applications are available from any
computer or any device—any time, anywhere.
Because most people are familiar with using the
Internet to find what they need, SaaS apps tend to
have high adoption rates, with a lower learning
curve.

•Lower initial Cost
SaaS applications are subscription based. No
license fees mean lower initial costs.
Having the SaaS provider manage the IT
infrastructure means lower IT costs for hardware,
software, and the people needed to manage it all.

•Painless Upgrades
Because the SaaS provider manages all
updates and upgrades, there are no patches for
customers to download or install.
The SaaS provider also manages availability,
so there’s no need for customers to add
hardware, software, or bandwidth as the user
base grows.

•Seamless Integration
SaaS vendors with true multitenant architectures
can scale indefinitely to meet customer demand.
 Many SaaS providers also offer customization
capabilities to meet specific needs.
Many provide APIs that let you integrate with
existing ERP systems or other business
productivity systems.

Although there are numerous benefits of a SaaS model there
are also some drawbacks to consider:
Security concerns:
One of the main inhibitors to cloud adoption is
access management and the privacy of sensitive
information.
With tokenization and encryption options available
this concern is becoming a thing of the past.

Compliance:
Certain countries and industries have regulation
relating to where data is stored.
Businesses need to ensure they comply with this and
implement a SaaS model that satisfies these
requirements.

Performance:
A browser-based application hosted remotely and
accessed via an internet connection is likely to worry
some businesses when compared to software running
on a local machine.
Obviously some tasks will be better suited to a SaaS
model than others, but with the advancements in
technology, internet connections have improved
severely over the past few years.

•Amazon Web Services (AWS)
•Windows Azure
•Google Compute Engine
•Rackspace Open Cloud
•IBM SmartCloud Enterprise
•HP Enterprise Converged Infrastructure
Infrastructure as a Service(IaaS)

Platform as a Service(PaaS)
• Engine Yard
•Red Hat OpenShift
•Google App Engine
•Windows Azure Cloud Services
•Amazon Web Services (AWS)

Software as a Service (SaaS)
•SaaS Customer Service Providers
•SaaS Office Suite Providers
•SaaS Project Management Providers
•SaaS Help Desk Providers

•NIST defines four deployment models:
private cloud
public cloud
community cloud
 hybrid cloud.

“The cloud infrastructure is operated solely for an
organization. It may be managed by the organization or a
third party and may exist on-premise or off-premise.”
•Private cloud gives an organization the benefits of cloud
computing, without the restrictions of network bandwidth,
security exposures, and legal issues that using external
resources might entail.
•It can also have better security, accountability, and
resilience than public cloud, because use can be controlled
and managed.

“The cloud infrastructure is made available to the general
public or a large industry group and is owned by an
organization selling cloud services.”
•Public cloud providers may offer some services free-of-
charge, but in general they charge enough on average to at
least cover their costs.
•The main benefit of using a public cloud, as opposed to
creating a private cloud, is easy and inexpensive set-up.
•The consumer also benefits from the economies of sharing
resources with other consumers

“The cloud infrastructure is shared by several organizations
and supports a specific community that has shared concerns
(e.g., mission, security requirements, policy, and compliance
considerations).”
•It can avoid network bandwidth, security exposures, and
legal issues that arise from using external resources, and its
use can be controlled and managed
•It makes set-up easy for individual organizations, and it
provides more efficient use of pooled resources for the whole
community than any of its members could achieve
individually.

“The cloud infrastructure is a composition of two or more
clouds (private, community, or public) that remain unique
entities but are bound together by standardized or
proprietary technology that enables data and application
portability .”
•A hybrid cloud may be coordinated by a broker that
federates data, identity, security, and other details.
•Another scenario is that an enterprise has a private cloud but
also uses a public cloud. In this model users typically host
non-business-critical information and processing in the public
cloud, while keeping business-critical services and data in
their control in the private part of the hybrid.

A cloud computing policy is meant to ensure that cloud
services are NOT used without the permission of the IT
Manager/CIO’s knowledge.
• Use of cloud computing services for formal purposes
should be authorised by the IT manager / CIO.
•The use of such services should comply with the
different policies of the company.
• For any service that requires the user to accept the
terms of service, such agreements should be reviewed
by the IT manager or CIO

•Employees should not share their login credentials with
their co-workers. The IT department will keep a document
confidential in nature containing account information for
business continuity
•The use of such services must comply with the policies
laid by the government.

Cloud By India- Meghraj (GI Cloud)
• GI Cloud is a set of discrete cloud computing
environments based on the existing and new
infrastructure and following a set of common
standards, guidelines and protocols which have been
issued by the Government of India.
•The cloud will be published by a single cloud service
directory

• The vision was to accelerate the delivery of e-services
and to optimise the ICT spending of the government
•Policy
 Evaluation of GI cloud for implementing all new projects
Existing application to be evaluated for moving to GI cloud.

• Policy Principles
 All clouds to follow guidelines and standards set by
Government of India.
All new applications to be cloud compatible.

Cloud By India- Meghraj (GI Cloud) Architecture

• The cloud computing environment at National and
State levels are known as National clouds and State
Clouds respectively.
• National Clouds will be built by utilizing the information
provided by the national data centre. Other national
clouds may also be built by augmenting the state data
centres
•Willing states cloud on the state data centre can
associate with the GI cloud

• The national cloud and each of the cloud at national
level are required to host the ‘eGov AppStore’ to host
and run application at National clouds.
• These platforms are easily customizable and
configurable for reuse by various government agencies
at centre/state without investing efforts in development
of such applications

Cloud By India- Meghraj (GI Cloud) Issues
S.No. Risk/Issue Description
1. Cloud Standards Existing cloud standards pertaining to
implementation, storage and migration
need to be interpreted to understand
their applicability for the GI Cloud
environment.
2. Security and
privacy
Risk of compromise of confidential
information and intellectual property
(IP). Risk of inappropriate access to
personal and confidential information

3. Application Design Traditional application design
approaches are different from cloud
based application design. All new
applications must be designed keeping
basic cloud design premises in mind.
4. Integration with
legacy environment
opportunity for customization of
existing applications and services may
be limited, leading to increased
complexity in integrating with existing
legacy environments.

5. Licensing Existing software licensing models may
not facilitate cloud deployment
especially from the point of cloud
service delivery.
6. Location of Data The dynamic nature of cloud may
result in uncertainty as to where data
actually resides (or where it is in
transit) at a given point in time. This
raises concerns related to data
ownership, accessibility, privacy and
security.

7. Portability Applications developed on one
platform may not be portable to, or
executable on another.
8. Loss of Control Loss of control may lead to resistance
to change. As the need to maintain
servers and other data centre
infrastructure diminishes, the form of
the IT function in government may
change.

9. Funding Model Due to the different funding models
like pay-per-use , subscription etc.,
some part of ICT capital budgeting will
need to be translated into operating
expenses (OPEX), as opposed to capital
expenditure (CAPEX). This will affect
budgeting for ICT and may have an
effect on the ICT procurement.

• On 30th December 2015, the Government of India issued an RFP
for cloud service offering of private service providers to accredit
themselves , so that the end user departments can leverage these
service offerings.
•This was in addition to the national cloud services provided by NIC
for their e-governance solution.
•The service providers have to confirm with the standards and
policies laid down by the government and have to get their cloud
service authorised by an auditor appointed by the Government of
India.

• Once the auditor approves ,the service provider is given a
provisional approval and after a period of 12 to 18 months a
permanent approval is provided.

• Cloud computing presents the opportunity to turn the IT
sector into a more effective, more responsive business service
and a source of business innovation.
•With on demand access to pool of trusted infrastructure and
services , cloud promise to decouple business initiatives from
the Information Technology capabilities needed to drive them
• Agile companies are seizing opportunities around the cloud
to create innovative business and service models that creates
operational efficiencies, decrease time to market and engage
customers in a new way.

• Whether an enterprise wants to consume or provide cloud
services, they can use the cloud to achieve new levels of
“Connected Experience” across customers, suppliers, partners
and employee relationships
•Everything spanning the corporate strategies, finance,
operations, governence, technologies and culture are
influenced by cloud

• Clients can leverage cloud to :
Transform IT
Scale and Streamline operations
Create new cloud based businesses

Create the IT platform of the future:
 Companies can use cloud technologies from
infrastructure through software to change the role of
long standing role of an IT from a custodian to an
orchestrator of business services
 This service oriented mindset requires a cultural shift
and a transition to a demand driven operating model

Transform Business Operations
 Companies can further derive value from cloud by
transforming internal business operations and
increasing operational performance.
They can use cloud through business applications
provided by Software as a Service in sales and
marketing, HR, and across the supply chain resulting in
greater agility across the enterprise

Create Profitable Cloud Businesses
 Cloud helps companies to innovate new products
and services to generate additional source of revenue,
to build the business cases and to transform their
business strategies.
 It also helps to foster new ways of customer
interactions to strengthen the competitive advantage.

• Cloud computing is set to transform how we do business
and move up the digital value chain.
• In India, the direct beneficial effect is on small to medium
sized businesses(SMB’s).
• The cloud computing market is expected to reach $4.5
Billion by the end of this year with most users being SMB’s as
quoted by Zinnov.
• According to another report if all SMB’s in India were to
adopt cloud computing, the market could reach $ 56 Billion.

• It is believed that companies like TCS,HCL, Infosys and Tech
Mahindra will bid for cloud computing providers rather than
developing solutions through their in house research, as it
requires huge funding.
•The competition among Indian service providers will have an
immense effect on the pricing of solutions

• The accessibility of broadband internet which is limited in
India is one of the key challenges
• With the rollout of Digital India, it would give a critical push
to enterprises to make the switch to cloud computing.
• With the launch of 100 Smart Cities, 500 rejuvenated cities
and numerous industrial hubs, a strong virtual backbone is a
necessity to take the development process to the next level.

• Skill formation for handling tasks of cloud computing is
important. We need to initiate course and popularize them
from the school level itself to get the desired result.
• It would give opportunities to millions to chose their field
with confidence that they can make a good career out of
cloud computing.

INFOSYS AND CLOUD
• Positions itself as a “Cloud Ecosystem Integrator“
• Comprehensive services for the cloud
• Business Platforms
• An Eco-system of Partnerships

Line of Business Functional Platforms
• Across Business verticals, Supporting enterprise initiatives
• For Digital Consumers
• Social Edge
• Brand Edge
• Smarter organizations
• Talent Edge
• Source-to-pay
• Emerging Economies
• Wallet edge
• Trade Edge

Vertical Platforms
• Specific requirements of specialized verticals
• Banking
• Retail
• Manufacturing
• Telecom
• Health
Bridge Platforms
• Niche Industries at the confluence of verticals
• For ex. Travel Insurance product

Cloud Computing.pptx

Recommended

Recommended

More Related Content

Similar to Cloud Computing.pptx

Similar to Cloud Computing.pptx (20)

Recently uploaded

Recently uploaded (20)

Cloud Computing.pptx