UNIT - III

CLOUD COMPUTING
ARCHITECTURE AND
MANAGEMENT
Cloud Computing

 CC refers to services like storage, databases, software,

analytics, and other platforms that are accessible via the
internet. It is any service that can be delivered without being
physically close to the hardware. For example, Netflix uses
cloud computing for its video streaming services. Another
example is G Suite, which runs entirely on the cloud.
 Cloud Computing refers to the delivery of on-demand
resources (such as a server, database, software, etc.) over the
internet. It also gives the ability to build, design, and manage
applications on the cloud platform.
Cloud Computing Service Providers

• AWS
• Microsoft Azure
• Google Cloud
• Alibaba Cloud
• IBM Cloud
• Oracle
• Salesforce
• SAP
• Rackspace Cloud
 VM Ware
Cloud Computing Architecture

 Cloud Computing Architecture is divided into two parts, i.e.,

front-end and back-end. Front-end and back-end
communicate via a network or internet.
 Front-End
• It provides applications and the interfaces that are required for
the cloud-based service.
• It consists of client’s side applications, which are web browsers
such as Google Chrome and Internet Explorer.
• Cloud infrastructure consists of hardware and software
components such as data storage, server, virtualization
software, etc.
• It also provides a Graphical User Interface to the end-users to
perform respective tasks.
Back-End
 It is responsible for monitoring all the programs that run the application on
the front-end
 It has a large number of data storage systems and servers.
 Application
• It can either be a software or a platform
• Depending upon the client requirement, the application provides the result to
the end-user (with resources) in the back end
 Service
• Service is an essential component in cloud architecture
• Its responsibility is to provide utility in the architecture
• In a Cloud, few widely used services among the end-users are storage
application development environments and web services
 Storage
• It stores and maintains data like files, videos, documents, etc. over the
internet
• Some of the popular examples of storage services are below:
• Amazon S3
• Oracle Cloud-Storage
• Microsoft Azure Storage
• Its capacity varies depending upon the service providers available in the
market
 Management
• Its task is to allot specific resources to a specific task, it simultaneously
performs various functions of the cloud environment
• It helps in the management of components like application, task,
service, security, data storage, and cloud infrastructure
• In simple terms, it establishes coordination among the cloud resources
 Security
• Security is an integral part of back-end cloud infrastructure
• It provides secure cloud resources, systems, files, and
infrastructure to end-users
• Also, it implements security management to the cloud server
with virtual firewalls which results in preventing data loss
 Benefits of Cloud Computing Architecture
 The cloud computing architecture is designed in such a way that:
• It solves latency issues and improves data processing requirements
• It reduces IT operating costs and gives good accessibility to access data
and digital tools
• It helps businesses to easily scale up and scale down their cloud
resources
• It has a flexibility feature which gives businesses a competitive
advantage
• It results in better disaster recovery and provides high security
• It automatically updates its services
• It encourages remote working and promotes team collaboration
Cloud Computing Architecture
Components

• Hypervisor
• Management Software
• Deployment Software
• Network
• Cloud Server
• Cloud Storage
Hypervisor

• It is a virtual machine monitor which provides Virtual

Operating Platforms to every user
• It also manages guest operating systems in the cloud
• It runs a separate virtual machine on the back end which
consists of software and hardware
• Its main objective is to divide and allocate resources
Management Software

• Its responsibility is to manage and monitor cloud operations

with various strategies to increase the performance of the cloud
• Some of the operations performed by the management
software are:
• compliance auditing-SLAs
• management of overseeing disaster
• contingency plans-minimizes customer inconvenience
 Deployment Software
• It consists of all the mandatory installations and configurations
required to run a cloud service
• Every deployment of cloud services are performed using a
deployment software
Cloud Storage

• Here, every bit of data is stored and accessed by a user from

anywhere over the internet
• It is scalable at run-time and is automatically accessed
• Data can be modified and retrieved from cloud storage over
the web
CLOUD ARCHITECTURE

 The cloud architecture can be divided into four layers

based on the access of the cloud by the user as follows :

1. Layer 1 (User/Client Layer)

2. Layer 2 (Network Layer)
3. Layer 3 (Cloud Management Layer)
4. Layer 4 (Hardware Resource Layer)
CLOUD ARCHITECTURE
CLOUD ARCHITECTURE
1 Layer 1 (User/Client Layer):

 This layer is the lowest layer in the cloud architecture. All

the users or client belong to this layer.
 This layer consists of client devices.
 The client/user initiates the connection to the cloud
through any device such as a thin client, thick client, or
mobile or any handheld device that would support basic
functionalities to access a web application.
 The thin client have very low processing capability.
 Thick clients are general computers that have adequate
processing capability.
 Cloud application can be accessed in the same way as a
web application.
CLOUD ARCHITECTURE
Layer 2 (Network Layer) :
 This layer allows the users to connect to the cloud.
 The whole cloud infrastructure is dependent on this
connection where the services are offered to the
customers.
 This is primarily the Internet in the case of a public
cloud.
 In the case of a private cloud, the connectivity may be
provided by a local area network (LAN).
 When accessing the public or private cloud, the users
require minimum bandwidth, which is sometimes
defined by the cloud providers.
CLOUD ARCHITECTURE
Layer 3 (Cloud Management Layer) :
 This layer consists of software that are used in managing
the cloud.
 The software can be a cloud operating system or a
management software that allows managing resources.
 These software usually allow resource management
(scheduling, provisioning, etc.), optimization (server
consolidation, storage workload consolidation), and
internal cloud governance.
 Any delay in processing or any discrepancy in service
provisioning may lead to an SLA violation.
 These SLAs are for both private and public clouds.
 Popular service providers are Amazon Web Services
(AWS) and Microsoft Azure for public cloud. Similarly,
OpenStack and Eucalyptus allow private cloud creation,
deployment, and management.
CLOUD ARCHITECTURE
Layer 4 (Hardware Resource Layer):
 Layer 4 consists of provisions for actual hardware
resources.
 In the case of a public cloud, a data center is used in the
back end.
 In a private cloud, it can be a data center, which is a huge
collection of hardware resources interconnected to each
other that is present in a specific location or a high
configuration system.
 If there is any discrepancy in provisioning the resources or
application, the service provider has to pay the penalty.
 The data center consists of a high-speed network
connection and a highly efficient algorithm to transfer the
data from the data center to the manager.
 There can be a number of data centers for a cloud, and
similarly, a number of clouds can share a data center.
ANATOMY OF THE CLOUD
 Cloud anatomy can be simply defined as the structure of
the cloud and it cannot be considered the same as cloud
architecture.
 Architecture is a hierarchical structural view that
defines the technology as well as the technology over
which it is dependent or/and the technology that are
dependent on it.
 Anatomy can be considered as a part of architecture.
 There are basically five components of the cloud:
ANATOMY OF THE CLOUD
ANATOMY OF THE CLOUD

 1. Application: The upper layer is the application layer. In this

layer, any applications are executed.
 2. Platform: This component consists of platforms that are
responsible for the execution of the application. This platform
is between the infrastructure and the application.
 3. Infrastructure: The infrastructure consists of resources over
which the other components work. This provides computational
capability to the user.
 4. Virtualization: Virtualization is the process of making logical
components of resources over the existing physical resources.
The logical components are isolated and independent, which
form the infrastructure.
 5. Physical hardware: The physical hardware is provided by
server and storage units.
Network Connectivity in
Cloud Computing
1. Public Cloud Access Networking
 In this the connectivity is often through the Internet, though some
cloud providers may be able to support virtual private networks (VPNs)
for customers.
 Accessing public cloud services will always create issues related to
security, which in turn is related to performance.
 One of the approaches to support of security is to promote
connectivity through encrypted tunnels, so that the information may
be sent via secure pipes on the Internet.
 This procedure will be an overhead in the connectivity, and using it will
certainly increase delay and may impact performance.
 To reduce the delay without compromising security, we have to select
a suitable routing method such as the one reducing the delay by
minimizing transit hops in the end-to-end connectivity between the
cloud provider and cloud consumer.
 Since the end-to-end connectivity support is via the Internet, one has
to look at the options of selecting the path.
Network Connectivity in
Cloud Computing
2. Private Cloud Access Networking
 In the private cloud deployment model, the cloud is part of an
organizational network, and the technology and approaches are
local to the in-house network structure.
 This may include an Internet VPN or VPN service from a
network operator.
 If the application access was properly done with an
organizational network—connectivity in a pre cloud
configuration—transition to private cloud computing will not
affect the access performance.
Network Connectivity in
Cloud Computing
3. Intracloud Networking for Public Cloud Services
 Here, the resources of the cloud provider and thus the
cloud service to the customer are based on the
resources that are geographically apart from each other
but still connected via the Internet.
 Public cloud computing networks are internal to the
service provider and thus not visible to the
user/customer; however, the security aspects of
connectivity and the access mechanisms of the
resources are important.
 The QoS issues in the connected resources world wide
are addressed in the SLAs commercially.
Network Connectivity in
Cloud Computing
4. Private Intracloud Networking
 The most complicated issue for networking and connectivity in cloud
computing is private intracloud networking.
 The complexity depends on how much intracloud connectivity is associated
with the applications being executed in this environment.
 Private intracloud networking is usually supported over connectivity between
the major data center sites owned by the company.
 At a minimum, all cloud computing implementations will rely on intracloud
networking to link users with the resource to which their application was
assigned.
 Once the resource linkage is made, the extent to which intracloud
networking is used depends on whether the application is componentized
based on service-oriented architecture (SOA) or not, among multiple systems.
 If the principle of SOA is followed, then traffic may move between
components of the application, as well as between the application and the
user.
 The impact of cloud computing performance is the differences that exist
between the current application and the network relationships with the
application.
 Private Intracloud Networking
 Bank Application-transaction failed –need data
 Finacle,ERP
 JAVA PHP
 SOA-Service oriented Architecture
Network Connectivity in
Cloud Computing
5. New Facets in Private Networks
 Conventional private networks have been architected for on-premise
applications and maximum Internet security.
 Typically, applications such as e-mail, file sharing, and enterprise resource
planning (ERP) systems are delivered to on-premise-based servers at each
corporate data center.
 Increasingly today, software vendors are offering Software as a Service
(SaaS) as an alternative for their software support to the corporate offices,
which brings more challenges in the access and usage mechanisms of software
from data center servers and in the connectivity of network architectures.
 The traditional network architecture for these global enterprises was not
designed to optimize performance for cloud applications.
 Now many applications including mission-critical applications are
transitioning (moving) from on-premise based to cloud based.
 Business cannot function if it cannot access applications such as ERP and e-
mail.
Network Connectivity in
Cloud Computing
6. Path for Internet Traffic
 The traditional Internet traffic through a limited set of Internet
gateways poses performance and availability issues for end users.
 It can be improved if a more widely distributed Internet gateway
infrastructure and connectivity are being supported for accessing
applications, as they will provide lower-latency access.
 As the volume of traffic to cloud applications grows, the
percentage of the legacy network’s capacity in terms of traffic to
regional gateways increases.
 Applications such as video conferencing would hog more
bandwidth while mission-critical applications such as ERP will
consume less bandwidth, and hence, one has to plan a correct
connectivity and path between providers and consumers.
APPLICATIONS ON THE CLOUD
Computer application evolution
STAND-ALONE APPLICATION

 The first type of applications that was developed and used

was a stand-alone application.
 It is developed to be run on a single system that does not use
network for its functioning.
 These systems do not need the data or processing power of
other systems; they are self-sustaining.
 The functioning of these kinds of systems is totally dependent
on the resources or features available within the system.
 Some examples are : Vlc media player, Adobe, photoshop
Notepad++, Google chrome
WEB APPLICATION
 Web application follows the client server architecture
with two basic components, called as the client and the
server.
 The server is a high-end machine that consists of the
web application installed.
 The client can reside anywhere in the network. It can
access the web application through the Internet.
 Unlike stand-alone applications, these systems were
totally dependent on the network for its working.
 This type of application was very useful, and this is
extensively used from its inception and now has become
an important part of day-to-day life.
 Examples : Online forms, shopping carts, word
processors, spreadsheets, video and photo editing, file
conversion, file scanning etc.
WEB APPLICATION
Shortcomings of web application :
 The web application is not elastic and it cannot serve highly
varying loads.
 The web application is not multitenant.
 The web application does not provide a quantitative
measurement of the services that are given to the users.
 The web applications are usually in one particular platform.
 The web applications are not provided on a pay-as-you-go
basis. A particular service is given to the user for permanent
or trial use.
 Due to its nonelastic nature, peak load transactions cannot be
handled.
CLOUD APPLICATION
 Cloud application in general refers to a SaaS
application.
 A cloud application usually can be accessed as a web
application but its properties differ.
 According to NIST, the features that make cloud
applications unique are :
1. Multitenancy
2. Elasticity
3. Heterogeneous cloud platform
4. Quantitative measurement
5. On-demand service
CLOUD APPLICATION FEATURES
CLOUD APPLICATION FEATURES
1. Multitenancy
 The software can be shared by different users with full
logical independence.
 There are no restrictions in the number of applications
being shared.If an application is physically too close,
then it becomes difficult to provide multitenancy.
CLOUD APPLICATION FEATURES
2. Elasticity
 Elasticity can be defined as the degree to which a
system is able to adapt to workload changes by
provisioning and deprovisioning resources in an
autonomic manner such that at each point in time, the
available resources match the current demand as
closely as possible.
 Elasticity allows the cloud providers to efficiently
handle the number of users.
 It supports the rapid fluctuation of loads, that is, the
increase or decrease in the number of users and their
usage can rapidly change.
CLOUD APPLICATION FEATURES
3. Heterogeneous cloud platform
 The cloud platform supports heterogeneity, wherein any
type of application can be deployed in the cloud.
 The cloud is flexible for the developers, which
facilitates deployment.
4. Quantitative measurement
 The services provided can be quantitatively measured.
 The application or resources are given as a utility on a
pay-per-use basis. Thus, the use can be monitored and
measured.
 The link usage and several other parameters that
support cloud applications can also be measured.
 This property of measuring the usage is usually not
available in a web application and is a unique feature
for cloud-based applications
CLOUD APPLICATION FEATURES
5. On-demand service
 The cloud applications offer service to the user, on
demand, that is, whenever the user requires it.
 The cloud service would allow the users to access web
applications usually without any restrictions on time,
duration, and type of device used.
Managing the Cloud

 Cloud management is aimed at efficiently managing the

cloud so as to maintain the QoS.
 The whole cloud is dependent on the way it is managed.
 Cloud management can be divided into two parts:
1. Managing the infrastructure of the cloud
2. Managing the cloud application
 Performance-QOS-Cloud service providers
 Funnctionality
 Cost
 Resource management
Managing the Cloud
Infrastructure
 The infrastructure of the cloud is considered to be the backbone
of the cloud and is mainly responsible for the QoS factor.
 If the infrastructure is not properly managed, then the whole
cloud can fail and QoS would be adversely affected.
 The core of cloud management is resource management which
includes resource scheduling, provisioning, and load
balancing.
 These tasks are mainly managed by the cloud service provider’s
core as the cloud OS.
 Cloud OS is responsible for providing services to the cloud and
that internally controls the cloud.
 Poor resource management may lead to several inefficiencies
in terms of performance, functionality, and cost.
 The SLAs can be satisfied only if performance is good.
 Even if there is a small discrepancy in providing the
functionality, the whole purpose of maintaining the cloud is
futile.
Managing the Cloud
Infrastructure
 A partially functional cloud would not satisfy the SLAs.
 if the cost of resource management is high, the service
provider would not bear the cost and hence the users have
to pay more. Hence, efficient management with less cost is
required.
 The power consumption and optimization of multiple
objectives will further reduce the cost.
 Consolidation of server and storage workloads would reduce
the energy consumption and in some cases would increase
the performance of the cloud.
 According to Margaret Rouse, server consolidation is an
approach to the efficient usage of computer server
resources in order to reduce the total number of servers or
server locations required. It is suitable for IaaS.
Managing the Cloud
Infrastructure
 Load fluctuation is one of the important criteria and
issues that should be considered for cloud applications.
 It be divided into two types: predictable and
unpredictable.
 Predictable load The cloud can be preconfigured for
handling Predictable load fluctuations.
 Unpredictable load fluctuations are difficult to handle.
 Cloud governance is another topic that is closely related
to cloud management
 Governance involves the process of creating value to an
organization by creating strategic objectives that will
lead to the growth of the company and would maintain
a certain level of control over the company.
 There are several aspects of cloud governance out of
which SLAs are one of the important aspects
governed.BY keeping these SLAs in mind
Managing the Cloud Application
 Moving the applications to the cloud environment brings new
complexities.
 Applications requires leveraging not only capabilities like storage and
database offered by the cloud providers but also third-party SaaS
capabilities like e-mail and messaging.
 Availability of an application requires inspecting the infrastructure,
the services it consumes, and the upkeep of the application.
 The composite nature of cloud applications requires visibility into all
the services to determine the overall availability and uptime.
 Cloud application management is to propose solutions to make it
possible to have insight into the application that runs in the cloud, as
well as implement or enforce enterprise policies like governance and
auditing and environment management while the application is
deployed in the cloud.
 These services can collect a multitude of events, analyze them, and
identify critical information that requires additional remedial actions
like adjusting capacity or provisioning new services.
 Additionally, application management has to be supported with tools
and processes required for managing other environments that might
coexist, enabling efficient operations.
Migrating Application to Cloud
Phases of Cloud Migration
 Moving one or more enterprise applications and their IT environments
from the traditional hosting type to the cloud environment(public,
private, or hybrid) is Cloud migration.
 Phases of Cloud Migration :
1. Evaluation: Evaluation is carried out for all the components like current
infrastructure and application architecture, environment in terms of
compute, storage, monitoring, and management, SLAs, operational
processes, financial considerations, risk, security, compliance, and
licensing needs are identified to build a business case for moving to the
cloud.
2. Migration strategy: Based on the evaluation, a migration strategy is
drawn.
 A hot plug strategy is used where the applications and their data and
interface dependencies are isolated, and these applications can be
operationalized all at once.
 A fusion strategy is used where the applications can be partially migrated;
but for a portion of it, there are dependencies based on existing licenses,
specialized server requirements like mainframes, or extensive
interconnections with other applications.
Phases of Cloud Migration
3. Prototyping: Migration activity is preceded by a prototyping
activity to validate and ensure that a small portion of the
applications are tested on the cloud environment with test
data setup.
4. Provisioning: Premigration optimizations identified are
implemented. Cloud servers are provisioned for all the
identified environments.
 necessary platform software and applications are deployed.
 Configurations are tuned to match the new environment
sizing, and databases and files are replicated.
 All internal and external integration points are properly
configured.
 Web services, batch jobs, and operation and management
software are set up in the new environments.
Phases of Cloud Migration

5. Testing: Postmigration tests are conducted to ensure

that migration has been successful which includes :
 Performance and load testing.
 Failure and recovery testing.
 Scale-out testing is conducted against the expected
traffic load and resource utilization levels.
Approaches for Cloud Migration
Four broad approaches adopted for cloud migration are :
1. Migrate existing applications:
 Rebuild or rearchitect some or all the applications, which
requires top engineers to develop new functionality.
 This can be achieved over the course of several releases with
the timing determined by customer demand.
2. Start from scratch:
 Rather than cannibalize sales, confuse customers with choice,
and tie up engineers trying to rebuild existing application, it
may be easier to start again.
 Many of the R&D decisions will be different now, and with
some of the more sophisticated development environments,
one can achieve more even with a small focused working
team.
 Approaches for Cloud Migration
3. Separate company: One may want to create a whole new
company with separate brand, management, R&D, and sales.
The investment and internet protocol (IP) may come from the
existing company, but many of the conflicts disappear once a
new born in the cloud company is established. The separate
company may even be a subsidiary of the existing company.
What is important is that the new company can act, operate,
and behave like a cloud-based start-up.
4. Buy an existing cloud vendor: For a large established vendor,
buying a cloud-based competitor achieves two things. Firstly,
it removes a competitor, and secondly, it enables the vendor
to hit the ground running in the cloud space. The risk of
course is that the innovation, drive, and operational approach
of the cloud-based company are destroyed as it is merged
into the larger acquirer.
THE SEVEN STEP MODEL OF
MIGRATION INTO CLOUD
ITERATIVE SEVEN STEP
MIGRATION MODEL
Review Questions

 1. What is server consolidation?

 2. How is cloud anatomy different from cloud
architecture?
 3. What are the unique properties of cloud
applications?
 4. What are the two different management
classifications?
 5. Why are SLAs important? Cloud Computing
Architecture and Management
 6. Describe several approaches of cloud migration.
Review Questions

 7. What is public cloud access networking?

 8. List the phases of cloud migration.
 9. What are the drawbacks of a web application?
 10. What is elasticity?
 11. Explain the pay-as-you-go paradigm
 UNIT - IV
CLOUD SERVICE MODE
CLOUD SERVICE MODELS
 CLOUD SERVICE MODELS
• Cloud computing is a model that enables the end users to access the
shared pool of resources such compute, network, storage,
database, and application as an on-demand service without the need
to buy or own it.
• The National Institute of Standards and Technology (NIST)
defines three basic service models, namely, IaaS, PaaS, and SaaS, as
shown in Figure 5.1.
• The NIST definition of the three basic service models is given as
follows:
• 1. IaaS: The ability given to the infrastructure architects to deploy
or run any software on the computing resources provided by the
service provider.
• 2. PaaS: The ability given to developers to develop and deploy an
application on the development platform provided by the service
provider.
• 3. SaaS: The ability given to the end users to access an application
over the Internet that is hosted and managed by the service provider.
INFRASTRUCTURE AS A
SERVICE (IAAS)
 INFRASTRUCTURE AS A
SERVICE (IAAS)
Compute: virtual central processing
units (CPUs) and
virtual main memory for the VMs
that are provisioned to the end users.
Storage: STaaS provides back-end
storage for the VM images.
Some of the IaaS providers also
provide the back end for storing files.
Network: Network as a Service (NaaS)
provides virtual networking
components such as virtual router,
switch, and bridge for the VMs.
Load balancers: Load Balancing as a
Service may provide load balancing
capability at the infrastructure layer.
INFRASTRUCTURE AS A
SERVICE (IAAS)
INFRASTRUCTURE AS A
SERVICE (IAAS)
Characteristics of IaaS:
 Web access to the resources:web browsers or management console.
 Centralized management:The resources distributed across different parts can be controlled
from any management console. EG:goole photos, drive,email etc
 Elasticity and dynamic scaling: IaaS provides elastic services where the usage of resources
can be increased or decreased according to the requirements.
 Shared infrastructure: IaaS follows a one-to-many delivery model and allows multiple IT
users to share the same physical infrastructure
. Preconfigured VMs: IaaS providers
offer preconfigured
VMs with operating systems (OSs),
network configuration, etc.
The IT users can select any kind of
VMs of their choice.

Metered services: IaaS allows the IT users to

rent the computing resources instead of buying it
. The services consumed by the IT user will be
measured, and the users will be charged
by the IaaS providers based on the amount of usage.
Suitability of IaaS
IaaS can be used in the following situations:
 Unpredictable spikes in usage:When demand is very volatile, we cannot predict
the spikes and troughs in terms of demand of the infrastructure.
 Limited capital investment:New start-up companies cannot invest more on buying
infrastructure for their business needs.
 Infrastructure on demand: Some organizations may require large infrastructure
for a short period of time. For this purpose, an organization cannot afford to buy
more on-premise resources
In following situations, IT users should avoid using the IaaS:
 When regulatory compliance does not allow off- premise hosting:
 When usage is minimal:
 When better performance is required:
 When there is a need for more control on physical infrastructure:
Pros and Cons of IaaS
Pro’s
•Reduced TCO
•Elastic resources
•Better resource utilization
•Supports Green IT
Con’s
•Security issues
•Interoperability issues
•Performance issues:Latency of the network plays an important role in
deciding the performance. Because of latency issues, sometimes
the VM contains issues with its performance.
 PLATFORM AS A SERVICE

 PaaS changes the way that the software is developed and deployed. In traditional
application development, the application will be developed locally and will be
hosted in the central location.

PAAS
 PaaS allows the developers to develop their application online and also allows
them to deploy immediately on the same platform. PaaS consumers or developers
can consume language runtimes, application - frameworks, databases, message
queues, testing tools, and deployment tools as a ser- vice over the Internet. Thus,
it reduces the complexity of buying and - maintaining different tools for developing
an application.
 Programming languages: PaaS providers provide a wide variety of programming
languages for the developers to develop applications.
 Some of the popular programming languages provided by PaaS vendors are java,
Perl, PHP, Python, Ruby, Scala, Clojure, and Go. Application frameworks: PaaS
vendors provide application frame-works that simplify the application
development.
 Some of the popular application development frameworks provided by a PaaS
provider include Node.js, Rails, Drupal, Joomla, WordPress, Django, EE6, Spring,
Play, Sinatra, Rack, and Zend.
 Database: Since every application needs to communicate with the databases, it
becomes a must-have tool for every application. PaaS providers are providing
databases also with their PaaS plat-forms.
 The popular databases provided by the popular PaaS ven-dors are ClearDB,
PostgreSQL, Cloudant, Membase, MongoDB, and Redis.
 Selecting a Region
Data
governance,
legal
requirements
Proximity to
customers
Determine the right (latency)

Region for your Services

available within
services, applications, the Region

and data based on these

Costs (vary by
factors
© 2019 Amazon Web Services, Inc. or its
Region)
69
Affiliates. All rights reserved.
 Availability Zones
• Each Region has multiple Availability AWS Cloud

Zones.
Region eu-west-1
• Each Availability Zone is a fully isolated Availability Zone eu-
partition of the AWS infrastructure. west-1a
Data
– There are currently 69 Availability Zones center
worldwide Data
center
– Availability Zones consist of discrete data centers Data
– They are designed for fault isolation center

– They are interconnected with other Availability Availability Zone eu-

Zones by using high-speed private networking west-1b

– You choose your Availability Zones. Availability Zone eu-

west-1c
– AWS recommends replicating data and
resources across Availability Zones for resiliency.
© 2019 Amazon Web Services, Inc. or its
70
Affiliates. All rights reserved.
 AWS data centers
• AWS data centers are designed for
security.
• Data centers are where the data
resides and data processing occurs.
• Each data center has redundant
power, networking, and
connectivity, and is housed in a
separate facility.
• A data center typically has 50,000 to
80,000 physical servers.

© 2019 Amazon Web Services, Inc. or its

71
Affiliates. All rights reserved.
 Points of Presence
• AWS provides a global
network of 187 Points of
Presence locations
• Consists of 176 edge
locations and 11
Regional edge caches
• Used with Amazon
CloudFront
– A global Content Delivery
Network (CDN), that
delivers content to end
users with reduced latency
• Regional edge caches
used for content with
infrequent access.

© 2019 Amazon Web Services, Inc. or its Affiliates. All 72

rights reserved.
 AWS infrastructure features
• Elasticity and scalability Physically Backup
distinct generato
• Elastic infrastructure; dynamic adaption
rs
of capacity
• Scalable infrastructure; adapts to Data center Data center Data center Data center

accommodate growth
Data center Data center Data center Data center

• Fault-tolerance Availability Zone Availability Zone

• Continues operating properly in the

presence of a failure
Data center Data center

• Built-in redundancy of components Network

connectivi
• High availability ty
Data center Data center

Availability Zone
• High level of operational performance
• Minimized downtime Uninterruptible Cooling
• No human intervention power supply AWS equipme
nt
© 2019 Amazon Web Services, Inc. or its
Region
73
Affiliates. All rights reserved.
Other tools: PaaS providers provide all the tools that are required to develop,
test, and deploy an application.
Characteristics of PaaS
All in one: Most of the PaaS providers offer services
develop, test, deploy, host, and maintain applications in the same IDE.

Web access to the development platform: A typical development plat-form uses

any IDEs for developing applications. Typically, the IDE will be installed in the
developer’s machines.
Offline access: A developer may not be able to connect to the Internet for a whole
day to access the PaaS services.
Built-in scalability: Scalability is an important requirement for the new-generation
web or SaaS applications. I
Collaborative platform: Nowadays, the development team consists of developers
who are working from different places.
Diverse client tools: To make the development easier, PaaS providers provide a
wide variety of client tools to help the developer. The client tools include CLI,
web CLI, web UI, REST API, and IDE.
Suitability of PaaS

 Collaborative development: To increase the time to market and development

efficiency, there is a need for a common place where the development team
and other stakeholders of the application can collaborate with each other.
 Automated testing and deployment: Automated testing and building of an
application are very useful while developing applications at a very short time
frame.
 Time to market: The PaaS services follow the iterative and incremental
development methodologies that ensure that the application is in the market
as per the time frame given.
situations where PaaS may not be the best option:
 Frequent application migration:
 Customization at the infrastructure level:
Pros and Cons of PaaS
Pro’s
Quick development and deployment: PaaS provides all the required development and
testing tools to develop, test, and deploy the soft-ware in one place.
Reduces TCO: The developers need not buy licensed development and testing tools if
PaaS services are selected.
Supports agile software development: Nowadays, most of the new-generation
applications are developed using agile methodologies.
Different teams can work together: The traditional development plat-form does not
have extensive support for collaborative development.
Ease of use: The traditional development platform uses any one of CLI- or IDEbased
interfaces for development.
Less maintenance overhead: In on-premise applications, the development company
or software vendor is responsible for maintaining the underlying hardware
Produces scalable applications: Most of the applications developed using PaaS
services are web application or SaaS application.
Con’s
Vendor lock-in: The major drawback with PaaS providers are vendor lock-in. The main
reason for vendor lock-in is lack of standards.
Security issues: Like in the other cloud services, security is one of the major issues in
PaaS services. Since data are stored in off--premise third-party servers, many
developers are afraid to go for PaaS services.
Less flexibility: PaaS providers do not give much freedom for the developers to define
their own application stack
Depends on Internet connection: Since the PaaS services are delivered over the
Internet, the developers should depend on Internet connectivity for developing the
application
SOFTWARE AS A SERVICE(SAAS)

SaaS provider may provide business services, social networks, document

management, and mail services as shown in above figure
 Business services: Most of the SaaS providers started providing a variety of
business services that attract start-up companies. The business SaaS services
include ERP, CRM, billing, sales, and human resources.
 Social networks: Since social networking sites are extensively used by the general
public, many social networking service providers adopted SaaS for their
sustainability.
 Document management: Since most of the enterprises extensively use electronic
documents, most of the SaaS providers started providing services that are used to
create, manage, and track electronic documents
 Mail services: E-mail services are currently used by many people. The future
growth in e-mail usage is unpredictable
Characteristics of SaaS
One to many: SaaS services are delivered as a one-to- many model where a single
instance of the application can be shared by multiple tenants or customers.
Web access: SaaS services provide web access to the software. It allows the end user
to access the application from any location if the device is connected to the
Internet.
Centralized management: Since SaaS services are hosted and man-aged from the
central location, management of the SaaS application becomes easier
 Multidevice support: SaaS services can be accessed from any end user devices
such as desktops, laptops, tablets, smart phones, and thin clients.
 Better scalability: Since most of the SaaS services leverage PaaS and IaaS for its
development and deployment, it ensures a better scalability than the traditional
software.
 High availability: SaaS services ensure the 99.99% availability of user data as
proper backup and recovery mechanisms are implemented at the back end.
 API integration: SaaS services have the capability of integrating with other
software or service through standard APIs
Suitability of SaaS
On-demand software: The licensing-based software model requires buying full
packaged software and increases the spending on buying software.
Software for start-up companies: When using any traditional software, the end user
should buy devices with minimum requirements specified by the software vendor
Software compatible with multiple devices: Some of the applications like word
processors or mail services need better accessibility from different- devices
Software with varying loads: We cannot predict the load on popular applications such
as social networking sites.
Real-time applications: Since SaaS applications depend on Internet connectivity, it
may not work better with low Internet speed.
 Applications with confidential data: Data security, data governance, and data
compliance are always issues with SaaS applications.
 Better on-premise application: Some of the on-premise applications might fulfill all
the requirements of the organization. In such situations, migrating to the SaaS model
may not be the best option.
Pros and Cons of SaaS
No client-side installation: SaaS services do not require client-side installation of the
software.
Cost savings: Since SaaS services follow the utility-based billing or pay-as-yougo billing,
it demands the end users to pay for what they have used.
Less maintenance: SaaS services eliminate the additional overhead of maintaining the
software from the client side.
Ease of access: SaaS services can be accessed from any devices if it is connected to the
Internet.
Dynamic scaling: SaaS services are popularly known for elastic dynamic scaling. It is very
difficult for on-premise software to pro-vide dynamic scaling capability as it requires
additional hardware
Disaster recovery: With proper backup and recovery mechanisms, replicas are
maintained for every SaaS services.
Multitenancy: Multitenancy is the ability given to the end users to share a single instance
of the application. Multitenancy increases resource utilization from the service
Cons’s
Security: Security is the major concern in migrating to SaaS application. Since the SaaS
application is shared between many end users, there is a possibility of data leakage
Connectivity requirements: SaaS applications require Internet connectivity for
accessing it. Sometimes, the end user’s Internet connectivity might be very slow.
Loss of control: Since the data are stored in a third-party and off-premise location, the
end user does not have any control over the data.