Professional Documents
Culture Documents
Script
Script
So to put it technically,
Cloud computing means that instead of all the computer hardware and software you're
using sitting on your desktop, or somewhere inside your company's network,
it's provided for you as a service by another company and accessed over the
Internet, usually in a completely seamless way.
Exactly where the hardware and software is located and how it all works doesn't
matter to you.
2)One benefit of using cloud computing services is that firms can avoid the upfront
cost and
complexity of owning and maintaining their own IT infrastructure,
and instead simply pay for what they use, when they use it.
3)In turn, providers of cloud computing services can benefit from significant
economies of scale by delivering the same services to a wide range of customers.
2)It's "on-demand"
Cloud services are available on-demand and often bought on a "pay-as-you go" or
subscription basis.
So you typically buy cloud computing the same way you'd buy electricity, telephone
services,
or Internet access from a utility company.
Sometimes cloud computing is free or paid-for in other ways (Hotmail is subsidized
by advertising, for example).
Just like electricity, you can buy as much or as little of a cloud computing
service as you need from one day to the next.
That's great if your needs vary unpredictably: it means you don't have to buy your
own gigantic computer system and risk have it sitting there doing nothing.
1)Iaas :
Infrastructure-as-a-Service (IaaS) refers to the fundamental building blocks of
computing that can be rented: physical or virtual servers, storage and networking.
This is attractive to companies that want to build applications from the very
ground up and want to control nearly all the elements themselves,
but it does require firms to have the technical skills to be able to orchestrate
services at that level.
Ordinary web hosting is a simple example of IaaS: you pay a monthly subscription or
a per-megabyte/gigabyte
fee to have a hosting company serve up files for your website from their servers.
2)Paas :
Platform-as-a-Service (PaaS) is the next layer up -- as well as the underlying
storage, networking,
and virtual servers this will also include the tools and software that developers
need
to build applications on top of: that could include middleware, database
management, operating systems, and development tools.
App Cloud (from salesforce.com) and the Google App Engine are examples of PaaS.
3)Saas :
Software-as-a-Service (SaaS) is the delivery of applications-as-a-service, probably
the version of cloud computing
that most people are used to on a day-to-day basis. The underlying hardware and
operating system is irrelevant
to the end user, who will access the service via a web browser or app; it is often
bought on a per-seat or per-user basis.
Best examples are office 365 provided by microsoft.
1)Public cloud:
Public cloud is the classic cloud computing model, where users can access a large
pool of computing power over the
internet (whether that is IaaS, PaaS, or SaaS). One of the significant benefits
here is the ability to rapidly scale a service.
The cloud computing suppliers have vast amounts of computing power, which they
share out between a large number of
customers -- the 'multi-tenant' architecture. Their huge scale means they have
enough spare capacity that they can easily cope if any particular customer needs
more resources,
which is why it is often used for less-sensitive applications that demand a varying
amount of resources.
2)Private cloud:
Private cloud allows organizations to benefit from the some of the advantages of
public cloud -- but without the concerns about relinquishing control over data and
services,
because it is tucked away behind the corporate firewall.Companies can control
exactly where their data is being held and can build the infrastructure in a way
they want -- largely for IaaS or PaaS projects -- to give developers access to a
pool of computing power that scales on-demand without putting security at risk.
3) Hybrid cloud.
In hybrid some data in the public cloud, some projects in private cloud, multiple
vendors and different levels of cloud usage.
The main reasons for choosing hybrid cloud include disaster recovery planning and
the desire to avoid hardware costs when expanding their existing data center.
Actually it turns out that is where the cloud really does matter; indeed
geopolitics is forcing significant changes on cloud computing user and vendors.
1)Firstly, there is the issue of latency: if the application is coming from a data
center on the other side of the planet, or on the other side of a congested
network,
then you may find it sluggish compared to a local connection. That's the latency
problem.
2)Secondly, there is the issue of data sovereignty. Many companies -- particularly
in Europe -- have to worry about where their data is being processed and stored.
European companies are worried that, for example, if their customer data is being
stored in data centers in the US or (owned by US companies) it could be accessed by
US law enforcement.
3)Cloud security is another issue; the UK government's cyber security agency has
warned that government agencies need to consider the country of origin when it
comes to adding cloud services into their supply chains.
While it was warning about antivirus software in particular, the issue is the same
for other types of services too.
Cloud computing services are operated from giant datacenters around the world.
AWS divides this up by 'regions' and 'availability zones'. Each AWS region is a
separate geographic area,
like EU (London) or US West (Oregon), which AWS then further subdivides into what
it calls availability zones (AZs).
An AZ is composed of one or more datacenters that are far enough apart that in
theory a single disaster won't take both offline,
but close enough together for business continuity applications that require rapid
failover.
Each AZ has multiple internet connections and power connections to multiple grids:
AWS has over 50 AZs.
Pros
1)Lower upfront costs and reduced infrastructure costs.
2)Easy to grow your applications.
3)Scale up or down at short notice.
4)Only pay for what you use.
5)Everything managed under SLAs.
6)Overall environmental benefit (lower carbon emissions) of many users efficiently
sharing large systems. (But see the box below.)
Cons
1)Higher ongoing operating costs. Could cloud systems work out more expensive?
2)Greater dependency on service providers. Can you get problems resolved quickly,
even with SLAs?
3)Risk of being locked into proprietary or vendor-recommended systems? How easily
can you migrate to another system or service provider if you need to?
4)What happens if your supplier suddenly decides to stop supporting a product or
system you've come to depend on?
5)Potential privacy and security risks of putting valuable data on someone else's
system in an unknown location?
6)If lots of people migrate to the cloud, where they're no longer free to develop
neat and whizzy new things, what does that imply for the future development of the
Internet?
7)Dependency on a reliable Internet connection.
1)Datalake
As we are moving in the world of IoT and machine learning to derive better and
informed business decisions,
data has become most valuable asset for organizations. From clickstreams to IoT,
mobile apps to social media and
data generated by business applications, it's all data. This amount of data is
massive and organizations are looking for a way to deal with it.
Consequently, data lakes are getting popular day by day.
Datalake
As we are moving in the world of IoT and machine learning to derive better and
informed business decisions,
data has become most valuable asset for organizations. From clickstreams to IoT,
mobile apps to social media
and data generated by business applications, it's all data. This amount of data is
massive and organizations
are looking for a way to deal with it. Consequently, data lakes are getting popular
day by day.
2) Infrastructure as a code:
It allows codification of infrastructure which helps in leveraging best software
development practices and
version control. It can be authored with any code editor like Visual Studio code or
Atom editor,
checked into a version control system like Git and reviewed with team members
before deployment into Dev/Test/Prod.