pract7
pract7
5. Theory:
• Self-service provisioning: End users can spin up computing resources for almost any
type of workload on-demand.
• Elasticity: Companies can scale up as computing needs increase and then scale down
again as demands decreases.
Pay per use: Computing resources are measured at a granular level, allowing users to
pay only for the resources and workloads they use.
Private cloud services are delivered from a business' data center to internal users. This
model offers versatility and convenience, while preserving management, control and
security. Internal customers may or may not be billed for services through IT
chargeback.
In the Public cloud model, a third-party provider delivers the cloud service over the
Internet. Public cloud services are sold on-demand, typically by the minute or the hour.
Customers only pay for the CPU cycles, storage or bandwidth they consume. Leading
public cloud providers include Amazon Web Services (AWS), Microsoft Azure,
IBM/SoftLayer and Google Compute Engine.
Hybrid cloud is a combination of public cloud services and on-premises private cloud
– with orchestration and automation between the two.
IT people talk about three different kinds of cloud computing, where different services
are being provided for you. Note that there's a certain amount of vagueness about how
these things are defined and some overlap between them.
Advantages: The pros of cloud computing are obvious and compelling. If your
business is selling books or repairing shoes, why get involved in the nitty gritty of
buying and maintaining a complex computer system? If you run an insurance office,
do you really want your sales agents wasting time running anti-virus software,
upgrading word-processors, or worrying about hard-drive crashes? Do you really
want them cluttering your expensive computers with their personal emails, illegally
shared MP3 files, and naughty YouTube videos—when you could leave that
responsibility to someone else? Cloud computing allows you to buy in only the
services you want, when you want them, cutting the upfront capital costs of
computers and peripherals. You avoid equipment going out of date and other
familiar IT problems like ensuring system security and reliability. You can add extra
services (or take them away) at a moment's notice as your business needs change.
It's really quick and easy to add new applications or services to your business
without waiting weeks or months for the new computer (and its software) to arrive.
If you're using software as a service (for example, writing a report using an online
word processor or sending emails through webmail), you need a reliable, high-
speed, broadband Internet connection functioning the whole time you're working.
That's something we take for granted in countries such as the United States, but it's
much more of an issue in developing countries or rural areas where broadband is
unavailable.
If you're buying in services, you can buy only what people are providing, so you
may be restricted to off-the-peg solutions rather than ones that precisely meet your
needs. Not only that, but you're completely at the mercy of your suppliers if they
suddenly decide to stop supporting a product you've come to depend on. (Google,
for example, upset many users when it announced in September 2012 that its cloud-
based Google Docs would drop support for old but de facto standard Microsoft
Office file formats such as .DOC, .XLS, and .PPT, giving a mere one week's
notice of the change—although, after public pressure, it later extended the deadline
by three months.) Critics charge that cloud-computing is a return to the bad-old days
of mainframes and proprietary systems, where businesses are locked into
unsuitable, long-term arrangements with big, inflexible companies. Instead of using
"generative" systems (ones that can be added to and extended in exciting ways the
developers never envisaged), you're effectively using "dumb terminals" whose uses
are severely limited by the supplier. Good for convenience and security, perhaps,
but what will you lose in flexibility? And is such a restrained approach good for the
future of the Internet as a whole? (To see why it may not be, take a look at Jonathan
Zittrain's eloquent book The Future of the Internet—And How to Stop It.)
6. Conclusion:
Cloud computing enables a convenient and on-demand network access to a wide
range of resources. The different services and also the deployment models allow
flexible service provider interaction with minimal human intervention. It saves
costs but also can lead to risk issues and suspension of resources when in huge
quantity.