Professional Documents
Culture Documents
issues Performance
issues
The name cloud computing was inspired by the cloud symbol that's often
used to represent the Internet in flowcharts and diagrams.
BENEFITS
The back end of the cloud computing architecture is the cloud itself,
comprising various computers, servers and data storage devices.
Hosting companies operate large data centers; and people who require
their data to be hosted buy or lease storage capacity from them and use
it for their storage needs.
This is the base layer of the cloud stack. It serves as a foundation for the
other two layers, for their execution. The keyword behind this stack is
Virtualization.
The whole cloud infrastructure viz. servers, routers, hardware based load-
balancing, firewalls, storage & other network equipments are provided by
the IaaS provider.
Some common examples are Amazon, GoGrid, 3 Tera, etc.
Platform as a Service (PaaS)
Community cloud:
The cloud infrastructure is shared by several
organizations and supports a specific community that has shared
concerns (e.g., mission, security requirements, policy).
Public cloud:
The cloud infrastructure is owned by an organization selling
cloud services to the general public or to a large industry group.
Hybrid cloud:
The cloud infrastructure is a composition of two or more
clouds that remain unique entities but are bound together by
standardized orproprietary technology.
ISSUES IN CLOUD COMPUTING
Security issues
- Physical security
- Operational security
- Programmatic security
Data issues
- Data backup
- Data usage
- Data loss
- Data integrity
- Data theft
Performance issue
Design issues
- Energy management
- Novel cloud architectures
- Software Licensing
Reliability
Legal issuues
- The Physical
Location of
your Data
- Responsibility
of your Data
- Intellectual
Property
SECURITY ISSUES
Data Integrity
When a data is on a cloud anyone from any location can access those data’s
from the cloud. Cloud does not differentiate between a sensitive data from a
common data thus enabling anyone to access those sensitive data’s. Thus there is a
lack of data integrity in cloud computing
Data Theft
Most of the cloud Vendors instead of acquiring a server tries to lease a server
from other service providers because they are cost affective and flexible for
operation.
The customer doesn’t know about those things, there is a high possibility that
the data can be stolen from the external server by a malicious user.
Security on Vendor level
Vendor should make sure that the server is well secured from all the external
threats it may come across. A Cloud is good only when there is a good security
provided by the vendor to the customers.
Information Security
Security related to the information exchanged between different
hosts or between hosts and users. This issues pertaining to secure
communication, authentication, and issues concerning single sign
on and delegation.
THERE MAY BE
Physical security :
- Physical location of data centers; protection of data centers
against disaster and intrusion.
Data Location
- When user use the cloud, user probably won't know exactly where
your data is hosted, what country it will be stored in?
•Traditional Security
VM-level attacks.
- Potential vulnerabilities in the VM technology used by cloud
vendors are a potential problem in multi-tenant architectures.
•Third-party data control
The legal implications of data and applications being held by a third party
are complex and not well understood. There is also a potential lack of
control and transparency when a third party holds the data.
All this is prompting some companies to build private clouds to avoid these
issues and yet retain some of the advantages of cloud computing.
Operational security
Organizations should require that any selected public cloud computing solution
is configured, deployed, and managed to meet their security, privacy, and other
requirements.
Governance :
Extend organizational practices pertaining to the policies,
procedures, and standards used for application development and service
provisioning in the cloud, as well as the design, implementation, testing, and
monitoring of deployed or engaged services.
Put in place audit mechanisms and tools to ensure
organizational practices are followed throughout the system lifecycle.
Compliance :
Understand the various types of laws and regulations that impose
security and privacy obligations on the organization.
Review and assess the cloud provider’s offerings with respect to the
organizational requirements to be met and ensure that the contract terms
adequately meet the requirements.
Data Protection :
Evaluate the suitability of the cloud provider’s data
management solutions for the organizational data concerned.
Availability :
Ensure that during an intermediate or prolonged disruption or a
serious disaster, critical operations can be immediately resumed and that all
operations can be eventually reinstituted in a timely and organized manner.
Trust :
Incorporate mechanisms into the contract that allow visibility into
the security and privacy controls and processes employed by the cloud
provider, and their performance over time.
Institute a risk management program that is flexible enough to
adapt to the continuously evolving and shifting risk landscape.
Identity and Access
Management Ensure that adequate safeguards are in place to
secure authentication, authorization, and other identity and access
management functions.
DATA ISSUES
Data Loss :-
Data loss is a very serious problem in Cloud computing. If the
vendor closes due to financial or legal problems there will be a loss of
data for the customers. The customers won’t be able to access those data’s
because data is no more available for the customer as the vendor shut
down.
Data Location :-
When it comes to location of the data nothing is transparent
even the customer don’t know where his own data’s are located. The
Vendor does not reveal where all the data’s are stored. The Data’s won’t
even be in the same country of the Customer, it might be located
anywhere in the world.
• Data Lock-In :-
Software stacks have improved interoperability among
platforms, but the APIs for Cloud Computing itself are still essentially
proprietary, or at least have not been the subject of active standardization.
Thus, customers cannot easily extract their data and
programs from one site to run on another.
For example, an online storage service called The Linkup shut
down on August 8, 2008 after losing access as much as 45% of customer
data [12]. The Linkup, in turn, had relied on the online storage service
Nirvanix to store customer data, and now there is finger pointing between
the two organizations as to why customer data was lost.
The obvious solution is to standardize the APIs so that a
SaaS developer could deploy services and data across multiple Cloud
Computing providers so that the failure of a single company would not
take all copies of customer data with it.
Data segregation :-
Data in the cloud is typically stored in a shared environment
whereby one customer’s data is stored alongside another customer’s data.
hence it is difficult to assure data segregation.
Introduction
Security issues
Performance issues
Cloud interoperability
tolerance Conclusion
WHY PERFOMANCE ?
PERFOMANCE ISSUES
• When companies or cloud vendors take the simplistic “more hardware solves
the problem” approach to cloud performance, they waste money.
• Hence, Adding virtual machines may be a short-term solution to the problem, but
adding machines is a manual task. If a company experiences a sudden spike in
traffic, how quickly will the vendor notice the spike and assign a technician to
provision more resources to the account?
• Storage, CPU, memory, and network bandwidth all come into play at
various times during typical application use.
• Therefore, one of the most common and costly responses to scaling issues
by vendors is to over-provision customer installations to accommodate a
wide range of performance issues.
To system performance through hardware
and software throughput gains is defeated
when a system is swamped by multiple,
simultaneous demands.
• That 10 gigabit pipe slows considerably when it serves hundreds of requests
rather than a dozen. The only way to restore higher effective throughput and
performance in such a “swamped resources” scenario is
to scale – add more of the resource that is overloaded.
HORIZONTAL SCALING :
But while the focus has been on cloud security, another potential
bottlenecks are on the way like – bandwidth requirement.
As enterprises start to move real workloads out to the cloud look for
bandwidth to become top of mind.
The problem arise when…
when you have dozens of developers all trying to use cloud
resources?
When you are trying to move a lot of video or graphics between your
business users and the cloud?
When this server is subjected to an extremely heavy load, the single App
Engine server appears to make connection and service every request that
arrives to an application at least partially, regardless of the number and
size.
Moreover, there are other crucial problems that arise from high power
consumption. Insufficient or malfunctioning cooling system can lead to
overheating of the resources reducing system reliability and devices
lifetime.
Finally, the data centers may be located in areas with widely different
outside temperatures, which have an impact on the amount of cooling
energy used.
Solutions :-
Geographical distribution of the data centers exposes many
opportunities for cost savings due to more energy consumption.
Finally, the data centers may be located in areas with widely different
outside temperatures, which have an impact on the amount of cooling
energy used.
Given the different characteristics of the data centers’ energy
consumptions, energy prices, and peak power prices, it becomes clear
that we can lower operating costs by intelligently placing (distributing)
the computational load across the wide area.
To reduce energy consumption and cost, each data center only keeps as
many servers active as necessary to service the current workload.
FAULT TOLERANCE
Fault tolerance (FT) policies can typically be listed into two sets:
reactive fault tolerance policies and proactive fault tolerance
policies.
The principle of proactive action is to avoid clouds from faults, errors and
failures by predicting them and proactively replace the suspected
components by other correctly working components providing the same
function.
There are some approach like. . .
approach is HA PROXY.
HA Proxy has the ability to perform this task by doing periodic health
checks on all the servers in a cluster. Even if one of the application servers
is not working, users will still have the availability to the application.
It monitors all the flow on the network and also health of different
servers whenever any server fails it will redirect user request to
another server and inform administrator about that faults.
Conclusion :
• It helps in convert CapEx into Opex . But every technology has pros
and cons cloud computing has also various issues associated with
it. . cloud computing provides many services like PaaS,IaaS,SaaS.
• There are many issues and solutions are highlighted in this topic
like security issues, privacy issues, data related issues, energy
related issues etc. We are using one of them services like Google
docs, Gmail but we do not find such issues related with it.
Hence I conclude that this issues comes consider whenever we
consider it with big level companies , they are not going to affect
much more as single user.
Some of the issues like bandwidth problems will not be longer due to
technology are increasing and speed will not affect longer. So there are
good scope in this field.