CLOUD COMPUTING

UNIT-2
(Cloud Enabling Technologies Service Oriented
Architecture)

Virtualization
Virtualization is the "creation of a virtual (rather than actual)
version of something, such as a server, a desktop, a storage device, an
operating system or network resources".
In other words, Virtualization is a technique, which allows to
share a single physical instance of a resource or an application among
multiple customers and organizations. It does by assigning a logical
name to a physical storage and providing a pointer to that physical
resource when demanded.

Creation of a virtual machine over existing operating system and

hardware is known as Hardware Virtualization. A Virtual machine
provides an environment that is logically separated from the underlying
hardware.
The machine on which the virtual machine is going to create is
known as Host Machine and that virtual machine is referred as a Guest
Machine

Need of Virtualization--There are five major needs of virtualization

which are described below:

1. ENHANCED PERFORMANCE-
Currently, the end user system i.e. PC is sufficiently
powerful to fulfill all the basic computation requirements of the user,
with various additional capabilities which are rarely used by the user.
Most of their systems have sufficient resources which can host a
virtual machine manager and can perform a virtual machine with
acceptable performance so far.

2. LIMITED USE OF HARDWARE AND SOFTWARE RESOURCES-

The limited use of the resources leads to under-utilization
of hardware and software resources. As all the PCs of the user are
sufficiently capable to fulfill their regular computational needs that’s
why many of their computers are used often which can be used 24/7
continuously without any interruption. The efficiency of IT
infrastructure could be increase by using these resources after hours for
other purposes. This environment is possible to attain with the help of
Virtualization.

3. SHORTAGE OF SPACE-
The regular requirement for additional capacity, whether
memory storage or compute power, leads data centers raise rapidly.
Companies like Google, Microsoft and Amazon develop their
infrastructure by building data centers as per their needs. Mostly,
enterprises unable to pay to build any other data center to
accommodate additional resource capacity. This heads to the diffusion
of a technique which is known as server consolidation.

4. ECO-FRIENDLY INITIATIVES-
At this time, corporations are actively seeking for various
methods to minimize their expenditures on power which is consumed
by their systems. Data centers are main power consumers and
maintaining a data center operations needs a continuous power supply
as well as a good amount of energy is needed to keep them cool for
well-functioning. Therefore, server consolidation drops the power
consumed and cooling impact by having a fall in number of servers.
Virtualization can provide a sophisticated method of server
consolidation.
5. ADMINISTRATIVE COSTS-
Furthermore, the rise in demand for capacity surplus, that
convert into more servers in a data center, accountable for a significant
increase in administrative costs. Hardware monitoring, server setup
and updates, defective hardware replacement, server resources
monitoring, and backups are included in common system
administration tasks. These are personnel-intensive operations. The
administrative costs is increased as per the number of servers.
Virtualization decreases number of required servers for a given
workload, hence reduces the cost of administrative employees.

Characteristics of Virtualization

Sharing –
Virtualization allows the creation of a separate computing
environment within the same host. This basic feature is used to reduce
the number of active servers and limit power consumption.
Aggregation –
It is possible to share physical resources among several guests,
but virtualization also allows aggregation, which is the opposite
process. A group of separate hosts can be tied together and represented
to guests as a single virtual host.
Emulation –
Guest programs are executed within an environment that is
controlled by the virtualization layer, which ultimately is a program.
Also, a completely different environment with respect to the host can
be emulated, thus allowing the execution of guest programs requiring
specific characteristics that are not present in the physical host.
Portability –
The concept of portability applies in different ways according
to the specific type of virtualization considered.
In the case of a hardware virtualization solution, the guest is packaged
into a virtual image that, in most cases, can be safely moved and
executed on top of different virtual machines.
In the case of programming-level virtualization, as implemented by the
JVM or the .NET runtime, the binary code representing application
components (jars or assemblies) can run without any recompilation on
any implementation of the corresponding virtual machine.
Resource sharing:
Virtualization allows multiple virtual machines to share the
resources of a single physical machine, such as CPU, memory, storage,
and network bandwidth. This improves hardware utilization and
reduces the need for additional physical servers.
Flexibility:
Virtualization allows IT administrators to quickly and easily
create, modify, or delete virtual machines as needed, without the need
to purchase and configure additional physical hardware.
Hardware independence:
Virtual machines are hardware-independent, which means
they can run on different types of physical hardware and can be easily
moved between physical servers without needing to reconfigure the
virtual machine.
Scalability:
Virtualization allows organizations to scale their computing
resources up or down as needed, depending on changing business
requirements.
Management:
Virtualization provides centralized management tools that
allow IT administrators to monitor and manage multiple virtual
machines from a single console, making it easier to troubleshoot and
maintain the virtualized environment.virtualization provides a
powerful and flexible technology that can help organizations maximize
their hardware utilization, improve their IT infrastructure scalability,
and simplify their IT management.
Disaster Recovery:
Virtualization enables organizations to implement disaster
recovery solutions more easily and cost-effectively. By replicating
virtual machines to remote sites, organizations can quickly recover
from a disaster and resume operations.
Testing and Development:
Virtualization allows organizations to easily create test and
development environments without the need for additional physical
hardware. This enables developers to test new applications and
configurations in a controlled environment before deploying them to
production.
Energy Efficiency:
Virtualization can help organizations reduce their energy
consumption by consolidating multiple physical servers onto a single
machine. This can result in lower electricity bills and a reduced carbon
footprint.
Cost Savings:
Virtualization can help organizations save money by reducing
the need for additional physical hardware, lowering electricity bills,
and streamlining IT operations. This can result in significant cost
savings over time.
Improved Security Management:
Virtualization can help organizations improve their security
posture by isolating applications and workloads from each other. This
can prevent security breaches from spreading to other parts of the
environment and reduce the attack surface.
Cloud Migration: Virtualization can be a stepping stone for
organizations looking to migrate to the cloud. By virtualizing their
existing infrastructure, organizations can make it easier to move
workloads to the cloud and take advantage of cloud-based services.

Drawback of Virtualization

High Initial Investment: Clouds have a very high initial investment,

but it is also true that it will help in reducing the cost of companies.
Learning New Infrastructure: As the companies shifted from Servers
to Cloud, it requires highly skilled staff who have skills to work with
the cloud easily, and for this, you have to hire new staff or provide
training to current staff.
Risk of Data: Hosting data on third-party resources can lead to putting
the data at risk, it has the chance of getting attacked by any hacker or
cracker very easily.

Hypervisor
The term “hypervisor”, coined in the 70s, was born from another term
traditionally used to refer to the kernel of an operating system (OS):
“supervisor”. By using the prefix “hyper-”, the “hypervisor” is
considered the supervisor of “supervisors”. A hypervisor, also known as
a Virtual Machine Monitor (VMM), is a layer of virtualization
software that allows the creation and running of several virtual
machines within a single server, as well as different operating systems.
The server where the hypervisor runs one or more virtual machines is
commonly known as a “host machine”, while each individual VM is
commonly known as a “guest machine”.
Hypervisors are in charge of separating the resources of the
virtual machine from the hardware system and of distributing them
properly. As an essential part of the technology supporting the cloud,
hypervisors make the migration to the cloud easier, enabling the
reduction of hardware expenditures and the increase of accessibility and
scalability inherent to the cloud.

Types of Hypervisor –
TYPE-1 Hypervisor:
The hypervisor runs directly on the underlying host system. It is also
known as a “Native Hypervisor” or “Bare metal hypervisor”. It does
not require any base server operating system. It has direct access to
hardware resources. Examples of Type 1 hypervisors include VMware
ESXi, Citrix XenServer, and Microsoft Hyper-V hypervisor.

Pros & Cons of Type-1 Hypervisor:

Pros: Such kinds of hypervisors are very efficient because they have
direct access to the physical hardware resources (like CPU, Memory,
Network, and Physical storage). This causes the empowerment of the
security because there is nothing any kind of the third party resource so
that attacker couldn’t compromise with anything.
Cons: One problem with Type-1 hypervisors is that they usually need
a dedicated separate machine to perform their operation and to instruct
different VMs and control the host hardware resources.

TYPE-2 Hypervisor:
A Host operating system runs on the underlying host system. It is also
known as ‘Hosted Hypervisor”. Such kind of hypervisors doesn’t run
directly over the underlying hardware rather they run as an application
in a Host system (physical machine). Basically, the software is
installed on an operating system. Hypervisor asks the operating system
to make hardware calls. An example of a Type 2 hypervisor includes
VMware Player or Parallels Desktop. Hosted hypervisors are often
found on endpoints like PCs. The type-2 hypervisor is very useful for
engineers, and security analysts (for checking malware, or malicious
source code and newly developed applications).
Pros & Cons of Type-2 Hypervisor:
Pros: Such kind of hypervisors allows quick and easy access to a guest
Operating System alongside the host machine running. These
hypervisors usually come with additional useful features for guest
machines. Such tools enhance the coordination between the host
machine and the guest machine.
Cons: Here there is no direct access to the physical hardware resources
so the efficiency of these hypervisors lags in performance as compared
to the type-1 hypervisors, and potential security risks are also there an
attacker can compromise the security weakness if there is access to the
host operating system so he can also access the guest operating system.

Types of Virtualization
Application Virtualization
Network Virtualization
Desktop Virtualization
Storage Virtualization
Server Virtualization or hardware virtualization
Data virtualization

Application Virtualization:
Application virtualization helps a user to have remote access
to an application from a server. The server stores all personal
information and other characteristics of the application but can still run
on a local workstation through the internet. An example of this would
be a user who needs to run two different versions of the same software.
Technologies that use application virtualization are hosted applications
and packaged applications.
Network Virtualization:
The ability to run multiple virtual networks with each having
a separate control and data plan. It co-exists together on top of one
physical network. It can be managed by individual parties that are
potentially confidential to each other. Network virtualization provides
a facility to create and provision virtual networks, logical switches,
routers, firewalls, load balancers, Virtual Private Networks (VPN), and
workload security within days or even weeks.

Desktop Virtualization:
Desktop virtualization allows the users’ OS to be remotely
stored on a server in the data center. It allows the user to access their
desktop virtually, from any location by a different machine. Users who
want specific operating systems other than Windows Server will need
to have a virtual desktop. The main benefits of desktop virtualization
are user mobility, portability, and easy management of software
installation, updates, and patches.

Storage Virtualization:
Storage virtualization is an array of servers that are
managed by a virtual storage system. The servers aren’t aware of
exactly where their data is stored and instead function more like
worker bees in a hive. It makes managing storage from multiple
sources be managed and utilized as a single repository. storage
virtualization software maintains smooth operations, consistent
performance, and a continuous suite of advanced functions despite
changes, breaks down, and differences in the underlying equipment.
Server Virtualization or hardware virtualization:
This is a kind of virtualization in which the masking of
server resources takes place. Here, the central server (physical server)
is divided into multiple different virtual servers by changing the
identity number, and processors. So, each system can operate its
operating systems in an isolated manner. Where each sub-server knows
the identity of the central server. It causes an increase in performance
and reduces the operating cost by the deployment of main server
resources into a sub-server resource. It’s beneficial in virtual
migration, reducing energy consumption, reducing infrastructural
costs, etc.
Software vendors use various techniques to implement server
virtualization or hardware virtualization. Which are as follows:-

1.Full Virtualization:-
In the full virtualization technique, the hypervisor completely
simulates the underlying hardware. The main advantage of this
technique is that it allows the running of the unmodified OS. In full
virtualization, the guest OS is completely unaware that it’s being
virtualized.
Full virtualization uses a combination of direct execution and binary
translation. This allows direct execution of non-sensitive CPU
instructions, whereas sensitive CPU instructions are translated on the fly.
To improve performance, the hypervisor maintains a cache of the
recently translated instructions.
VMware’s ESXi server uses this technique to achieve server
virtualization.
2.Paravirtualization
In paravirtualization, the hypervisor doesn’t simulate
underlying hardware. Instead, it provides hypercalls. The guest OS
uses hypercalls to execute sensitive CPU instructions. This technique is
not as portable as full virtualization, as it requires modification in the
guest OS. However, it provides better performance because the guest OS
is aware that it’s being virtualized.
Hypercalls are similar to kernel system calls. They allow the guest OS to
communicate with the hypervisor.
The open-source Xen project uses the paravirtualization technique.

3.Hardware-assisted Virtualization:-
Also known as native virtualization, in this
technique, underlying hardware provides special CPU instructions to
aid virtualization. This technique is also highly portable as the
hypervisor can run an unmodified guest OS. This technique makes
hypervisor implementation less complex and more maintainable.
Intel’s Intel-VT and AMD’s AMD-V processors provide CPU
virtualization instructions that software vendors use to implement
hardware-assisted virtualization.

Data Virtualization:
This is the kind of virtualization in which the data is collected
from various sources and managed at a single place without knowing
more about the technical information like how data is collected, stored &
formatted then arranged that data logically so that its virtual view can be
accessed by its interested people and stakeholders, and users through the
various cloud services remotely. Many big giant companies are
providing their services like Oracle, IBM, At scale, Cdata, etc.
Implementation Levels of Virtualization
It is not simple to set up virtualization. Your computer runs on
an operating system that gets configured on some particular hardware. It
is not feasible or easy to run a different operating system using the same
hardware.
To do this, you will need a hypervisor. Now, what is the role
of the hypervisor? It is a bridge between the hardware and the virtual
operating system, which allows smooth functioning.
Talking of the Implementation levels of virtualization in Cloud
Computing., there are a total of five levels that are commonly used.
Let us now look closely at each of these levels of
virtualization implementation in Cloud Computing.
1. Instruction Set Architecture Level (ISA) ISA virtualization can work
through ISA emulation. ...
2.Hardware Abstraction Level (HAL) ...
3. Operating System Level. ...
4.Library Level. ...
5.Application Level

1) Instruction Set Architecture Level (ISA)

ISA virtualization can work through ISA emulation. This is used to run
many legacy codes written for a different hardware configuration. These
codes run on any virtual machine using the ISA. With this, a binary code
that originally needed some additional layers to run is now capable of
running on the x86 machines. It can also be tweaked to run on the x64
machine. With ISA, it is possible to make the virtual machine hardware
agnostic.
For the basic emulation, an interpreter is needed, which interprets the
source code and then converts it into a hardware format that can be read.
This then allows processing. This is one of the five implementation
levels of virtualization in Cloud Computing..

2) Hardware Abstraction Level (HAL)

True to its name HAL lets the virtualization perform at the level of the
hardware. This makes use of a hypervisor which is used for functioning.
The virtual machine is formed at this level, which manages the hardware
using the virtualization process. It allows the virtualization of each of the
hardware components, which could be the input-output device, the
memory, the processor, etc.
Multiple users will not be able to use the same hardware and also use
multiple virtualization instances at the very same time. This is mostly
used in the cloud-based infrastructure.

3) Operating System Level

At the level of the operating system, the virtualization model is capable
of creating a layer that is abstract between the operating system and the
application. This is an isolated container on the operating system and the
physical server, which uses the software and hardware. Each of these
then functions in the form of a server.
When there are several users and no one wants to share the hardware,
then this is where the virtualization level is used. Every user will get his
virtual environment using a dedicated virtual hardware resource. In this
way, there is no question of any conflict.

4) Library Level
The operating system is cumbersome, and this is when the applications
use the API from the libraries at a user level. These APIs are
documented well, and this is why the library virtualization level is
preferred in these scenarios. API hooks make it possible as it controls
the link of communication from the application to the system.

5) Application Level
The application-level virtualization is used when there is a desire to
virtualize only one application and is the last of the implementation
levels of virtualization in Cloud Computing. One does not need to
virtualize the entire environment of the platform.
This is generally used when you run virtual machines that use high-level
languages. The application will sit above the virtualization layer, which
in turn sits on the application program.
It lets the high-level language programs compiled to be used at the
application level of the virtual machine run seamlessly.

Conclusion
There are in total of five implementation levels of virtualization in Cloud
Computing. However, every enterprise may not use each one of the
different levels of virtualization implementation in Cloud Computing.
The level used is based on the working of the company and also on its
preference for the level of virtualization. The company will use the
virtual machine to develop and test across multiple platforms. Cloud-
based applications are on the rise, making virtualization a must-have
thing for enterprises worldwide.

virtual disaster recovery

Virtual disaster recovery refers to the use of virtualized
workloads for disaster recovery planning and failover. To achieve this,
organizations need to regularly replicate workloads to an offsite virtual
disaster recovery site.
For enterprises in virtual environments, VM replication provided by
hypervisor vendors may be enough. As for physical or hybrid
environments, physical to virtual conversion (P2V) is still needed
before replication.

Service-Oriented Architecture (SOA)

Service-oriented architecture (SOA) is a method of
software development that uses software components called services to
create business applications. Each service provides a business capability,
and services can also communicate with each other across platforms and
languages. Developers use SOA to reuse services in different systems or
combine several independent services to perform complex tasks.
For example, multiple business processes in an organization
require the user authentication functionality. Instead of rewriting the
authentication code for all business processes, you can create a single
authentication service and reuse it for all applications. Similarly, almost
all systems across a healthcare organization, such as patient management
systems and electronic health record (EHR) systems, need to register
patients. These systems can call a single, common service to perform the
patient registration task.

The different characteristics of SOA are as follows :

o Provides interoperability between the services.
o Provides methods for service encapsulation, service discovery,
service composition,
service reusability and service integration.
o Facilitates QoS (Quality of Services) through service contract based
on Service Level
Agreement (SLA).
o Provides loosely couples services.
o Provides location transparency with better scalability and
availability.
o Ease of maintenance with reduced cost of application development
and deployment.

Guiding Principles of SOA:

Standardized service contract (SSC): Specified through one or more
service description documents.
Loose coupling: Services are designed as self-contained components,
maintain relationships that minimize dependencies on other services.
Abstraction: A service is completely defined by service contracts and
description documents. They hide their logic, which is encapsulated
within their implementation.
Reusability: Designed as components, services can be reused more
effectively, thus reducing development time and the associated costs.
Autonomy: Services have control over the logic they encapsulate and,
from a service consumer point of view, there is no need to know about
their implementation.
Discoverability: Services are defined by description documents that
constitute supplemental metadata through which they can be
effectively discovered. Service discovery provides an effective means
for utilizing third-party resources.
Composability: Using services as building blocks, sophisticated and
complex operations can be implemented. Service orchestration and
choreography provide a solid support for composing services and
achieving business goals.

Architecture of SOA:-

Service provider:-
The service provider creates, maintains, and provides one or more
services that others can use. Organizations can create their own services
or purchase them from third-party service vendors.
Service consumer:-
The service consumer requests the service provider to run a
specific service. It can be an entire system, application, or other service.
The service contract specifies the rules that the service provider and
consumer must follow when interacting with each other. Service
providers and consumers can belong to different departments,
organizations, and even industries.
Service registry:-
A service registry, or service repository, is a network-accessible
directory of available services. It stores service description documents
from service providers. The description documents contain information
about the service and how to communicate with it. Service consumers
can easily discover the services they need by using the service registry.
Web service providers publish their web services on web-service
registries. The service consumer searches for web services by querying
the broker. Finally the service consumer incorporates the web-services
in his application and invokes them when needed.

How does service-oriented architecture work?

In service-oriented architecture (SOA), services function independently
and provide functionality or data exchanges to their consumers. The
consumer requests information and sends input data to the service. The
service processes the data, performs the task, and sends back a response.
For example, if an application uses an authorization service, it gives the
service the username and password. The service verifies the username
and password and returns an appropriate response.
Communication protocols
Services communicate using established rules that determine data
transmission over a network. These rules are called communication
protocols. Some standard protocols to implement SOA include the
following:
• Simple Object Access Protocol (SOAP)
• RESTful HTTP
• Apache Thrift
• Apache ActiveMQ
• Java Message Service (JMS)
You can even use more than one protocol in your SOA implementation.

Advantages of SOA:
Service reusability: In SOA, applications are made from existing
services. Thus, services can be reused to make many applications.
Easy maintenance: As services are independent of each other they can
be updated and modified easily without affecting other services.
Platform independent: SOA allows making a complex application by
combining services picked from different sources, independent of the
platform.
Availability: SOA facilities are easily available to anyone on request.
Reliability: SOA applications are more reliable because it is easy to
debug small services rather than huge codes
Scalability: Services can run on different servers within an
environment, this increases scalability

Disadvantages of SOA:
High overhead: A validation of input parameters of services is done
whenever services interact this decreases performance as it increases
load and response time.
High investment: A huge initial investment is required for SOA.
Complex service management: When services interact they exchange
messages to tasks. the number of messages may go in millions. It
becomes a cumbersome task to handle a large number of messages.
Practical applications of SOA: SOA is used in many ways
around us whether it is mentioned or not.
1. SOA infrastructure is used by many armies and air forces to deploy
situational awareness systems.
2. SOA is used to improve healthcare delivery.
3. Nowadays many apps are games and they use inbuilt functions to
run. For example, an app might need GPS so it uses the inbuilt GPS
functions of the device. This is SOA in mobile solutions.
4. SOA helps maintain museums a virtualized storage pool for their
information and content.

Layered architecture of Service Oriented Architecture

(SOA)

SOA Layer or Framework consist of two-layer: horizontal

layers and vertical layers.
SOA Horizontal Layers
5 different SOA horizontal layers which are:
Consumer interface layer: These are GUI app for user to access the
services.
Business process layer: It is a service layer that represents the business
use case and business processes.
Services layer: Many service work together for creating a whole
enterprise in service inventory.
Application layer: This layer contains the data models, technical
patterns and data repository, adapters etc.
Technology layer: like technological interfaces, functional and
technical libraries, etc.

SOA Vertical Layers

The following are the vertical layers of SOA framework
Integration layer: This layer enables the integration of services through
the introduction of a reliable set of capabilities, such as intelligent
routing, protocol mediation, and other transformation mechanisms
Quality of service: This layer provides the capabilities required to
monitor, manage, and maintain QoS such as security, performance, and
availability. This is a background process through sense-and-respond
mechanisms and tools that monitor the health of SOA applications.
Governance: also known as IT strategy layer is governed by horizontal
layers in order to reach required operational capability as needed.

Web Service
Web service is a standardized medium to propagate
communication between the client and server applications on the WWW
(World Wide Web). A web service is a software module that is designed
to perform a certain set of tasks.
Web services in cloud computing can be searched for over the network
and can also be invoked accordingly.
When invoked, the web service would be able to provide the
functionality to the client, which invokes that web service.

How WebServices Work?

The above diagram shows a very simplistic view of how a web service
would actually work. The client would invoke a series of web service
calls via requests to a server which would host the actual web service.
These requests are made through what is known as remote procedure
calls. Remote Procedure Calls(RPC) are calls made to methods which
are hosted by the relevant web service.
As an example, Amazon provides a web service that provides prices for
products sold online via amazon.com. The front end or presentation
layer can be in .Net or Java but either programming language would
have the ability to communicate with the web service.

Why do you need a Web Service?Modern day business

applications use variety of programming platforms to develop web-
based applications. Some applications may be developed in Java, others
in .Net, while some other in Angular JS, Node.js, etc.
Most often than not, these heterogeneous applications need some sort of
communication to happen between them. Since they are built using
different development languages, it becomes really difficult to ensure
accurate communication between applications.
Here is where web services come in. Web services provide a common
platform that allows multiple applications built on various programming
languages to have the ability to communicate with each other.

Web Services Architecture:-

Every framework needs some sort of architecture to make sure the entire
framework works as desired, similarly, in web services.
The Web Services Architecture consists of three distinct roles as
given below:
Provider – The provider creates the web service and makes it available
to client applications who want to use it.
Requestor – A requestor is nothing but the client application that needs
to contact a web service. The client application can be a .Net, Java, or
any other language based application which looks for some sort of
functionality via a web service.
Broker – The broker is nothing but the application which provides
access to the UDDI. The UDDI,enables the client application to locate
the web service.

The diagram below showcases how the Service provider, the Service
requestor and Service registry interact with each other.
Publish – A provider informs the broker (service registry) about the
existence of the web service by using the broker’s publish interface to
make the service accessible to clients
Find – The requestor consults the broker to locate a published web
service
Bind – With the information it gained from the broker(service registry)
about the web service, the requestor is able to bind, or invoke, the web
service.

Type of Web Services:-

There are mainly two types of web services.

1.SOAP web services.
2.RESTful web services.

SOAP Web Services

SOAP stands for Simple Object Access Protocol. It is a XML-based
protocol for accessing web services.
SOAP is a W3C recommendation for communication between two
applications.
SOAP is XML based protocol. It is platform independent and language
independent. By using SOAP, you will be able to interact with other
programming language applications.
Advantages of Soap Web Services:-
WS Security: SOAP defines its own security known as WS Security.
Language and Platform independent: SOAP web services can be
written in any programming language and executed in any platform.

Disadvantages of Soap Web Services:-

Slow: SOAP uses XML format that must be parsed to be read. It defines
many standards that must be followed while developing the SOAP
applications. So it is slow and consumes more bandwidth and resource.
WSDL dependent: SOAP uses WSDL and doesn't have any other
mechanism to discover the service.

REST(Representational State Transfer):-

REST stands for REpresentational State Transfer and API stands
for Application Program Interface. REST is a software architectural
style that defines the set of rules to be used for creating web services.
Web services which follow the REST architectural style are known as
RESTful web services. It allows requesting systems to access and
manipulate web resources by using a uniform and predefined set of
rules. Interaction in REST based systems happen through Internet’s
Hypertext Transfer Protocol (HTTP).

A Restful system consists of a:

1.client who requests for the resources.
2.server who has the resources.

It is important to create REST API according to industry standards

which results in ease of development and increase client adoption.
REST became popular due to the following reasons:
It allows web applications built using different programming
languages to communicate with each other. Also, web applications
may reside in different environments, like on Windows, or for
example, Linux.
Mobile devices have become more popular than desktops. Using
REST, you don’t need to worry about the underlying layer for the
device. Therefore, it saves the amount of effort it would take to code
applications on mobiles to talk with normal web applications.
Modern applications have to be made compatible with the Cloud. As
Cloud-based architectures work using the REST principle, it makes
sense for web services to be programmed using the REST service-
based architecture.

Architectural Constraints of RESTful API:

There are six architectural constraints which makes any web service
are listed below:
1. Uniform Interface
2. Stateless
3. Cacheable
4. Client-Server
5. Layered System
6. Code on Demand

he only optional constraint of REST architecture is code on demand. If

a service violates any other constraint, it cannot strictly be referred to
as RESTful.

1.Uniform Interface: It is a key constraint that differentiate between a

REST API and Non-REST API. It suggests that there should be an
uniform way of interacting with a given server irrespective of device or
type of application (website, mobile app).

There are four guidelines principle of Uniform Interface are:

a. Resource-Based: Individual resources are identified in requests. For
example: API/users.
b. Manipulation of Resources Through Representations: Client has
representation of resource and it contains enough information to
modify or delete the resource on the server, provided it has permission
to do so. Example: Usually user get a user id when user request for a
list of users and then use that id to delete or modify that particular user.
c. Self-descriptive Messages: Each message includes enough
information to describe how to process the message so that server can
easily analyses the request.
d. Hypermedia as the Engine of Application State (HATEOAS): It
need to include links for each response so that client can discover other
resources easily.
2. Stateless: It means that the necessary state to handle the request is
contained within the request itself and server would not store anything
related to the session. In REST, the client must include all information
for the server to fulfill the request whether as a part of query headers or
URI. Statelessness enables greater availability since the server does not
have to maintain, update or communicate that session state. There is a
drawback when the client need to send too much data to the server so it
reduces the scope of network optimization and requires more
bandwidth.
Cacheable: Every response should include whether the response is
cacheable or not and for how much duration responses can be cached
at the client side. Client will return the data from its cache for any
subsequent request and there would be no need to send the request
again to the server. A well-managed caching partially or completely
eliminates some client–server interactions, further improving
availability and performance. But sometime there are chances that user
may receive stale data.
Client-Server: REST application should have a client-server
architecture. A Client is someone who is requesting resources and are
not concerned with data storage, which remains internal to each server,
and server is someone who holds the resources and are not concerned
with the user interface or user state. They can evolve independently.
Client doesn’t need to know anything about business logic and server
doesn’t need to know anything about frontend UI.
Layered system: An application architecture needs to be composed of
multiple layers. Each layer doesn’t know anything about any layer
other than that of immediate layer and there can be lot of intermediate
servers between client and the end server. Intermediary servers may
improve system availability by enabling load-balancing and by
providing shared caches.
Code on demand: It is an optional feature. According to this, servers
can also provide executable code to the client. The examples of code
on demand may include the compiled components such as Java
Servlets and Server-Side Scripts such as JavaScript.
Advantages of REST:-
Speed: As there is no strict specification, RESTful web services are
faster as compared to SOAP. It also consumes fewer resources and
bandwidth.
Compatible with SOAP: RESTful web services are compatible with
SOAP, which can be used as the implementation.
Language and Platform Independency: RESTful web services can
be written in any programming language and can be used on any
platform.
Supports Various Data Formats: It permits the use of several data
formats like HTML, XML, Plain Text, JSON, etc.

Disadvantages of a REST :-
Although REST APIs have many advantages, they also have some
disadvantages that you should be aware of, especially if you are looking
to specialize in web development.
Some of the main disadvantages are:
1. Increased design complexity:-
Although they are easier to use, the design of a REST API can be more
complex than other APIs, especially if you are not familiar with web
architecture.
The REST API uses architectural principles that you need to be familiar
with in order to develop your API.
2. Web connection:-
All changes to your REST API must be executed on the web and only on
the web. It’s impossible to edit the API from your desktop without an
internet connection, unlike HTML web files, for example. You must
always connect to make the slightest change.
A REST API requires an Internet connection to function, which means it
may be less useful in offline environments.
 3. Variable performance and flexibility:-
On the other hand, REST APIs can have slightly lower performance than
other APIs, depending on the servers and their internet speed.

SOAP vs REST Web Services:-

There are many differences between SOAP and REST web services. The
important 10 differences between SOAP and REST are given below:
N SOAP REST
o

1) SOAP is a protocol. REST is an architectural style.

2) SOAP stands for Simple Object REST stands for Representational State Transfer.
Access Protocol.

3) SOAP can't use REST because REST can use SOAP web services because it is a conc
it is a protocol. and can use any protocol like HTTP, SOAP.

4) SOAP uses services interfaces REST uses URI to expose business logic.
to expose the business logic.

5) JAX-WS is the java API for JAX-RS is the java API for RESTful web services.
SOAP web services.

6) SOAP defines standards to be REST does not define too much standards like SOAP.
strictly followed.

7) SOAP requires more REST requires less bandwidth and resource than SOAP
bandwidth and resource than
REST.

8) SOAP defines its own security. RESTful web services inherits security measures from
 underlying transport.

9) SOAP permits XML data REST permits different data format such as Plain text,
format only. HTML, XML, JSON etc.

1 SOAP is less preferred than REST more preferred than SOAP.

0) REST.
 Vistaligaton cf cPu, Memony ar I/0 levices ’
Vshalyation of cou

Lnuy
Wmdows
huest os2
Gvest os)
yhev'san (vmm )
CpU
Host as t as
imvoLves a omgls cpu athing
CPU Viortealizotonsehenate cpUs. b allow% dm 0S to
mutplu þowen t'n
Wee
vtilye he cpu
effechey aond efiuetly
the Computen sothat t ns feste
Alt he scgrans and Lmstchons ae gUming physital
gwing he feeling like
torougf virval machine ae bandled by G)
wosstato Al the oberatons
trols oftae to tUn attodtng
emulata hat (on
to it.
Yhes of cA vrhlyahon
based cr virtaligahon.
+ Sofhwas Vittohahon.
Handcsaot Assisted GU
cpU vitalzahon2 Tn tt aelcaton
Softuae based Ccole gets exeUted
Oon the foocesaT aod the kinidged cocde gets tons
Aated nst and that tnoqslated Code gets exewted.
 oon he gcess0r.
socess
kyoCéss VkAd hu ts
is nown ds
The r0avs latron

Hardwane Assisted CPU voalizdhon ’

Ton tt, Hhe handwas gets asistonce foon
Certan stocessoss, but t dlso teapes hybeviSO7
fon couahng viontel machine.
iuqyuseoment of tmsaton.
calls dse Ußed in tt hch suns feste
goten
-than egbected. Jstogtom
fpogrom
s q tunction hat a vser
Cvote- Syotem call Aoss q becticuan serv'ce)
Uses to ask the os
Viatvalzton of menany
Gruest vibrtval memany
vm1Vmevm3 Gruest bhys'cal memcy
HyhenvisoH(Vmm)

Cbhysical muomony)
virtv aligahon to the psoces of onscl'dact'ng
Meamay UsOU1(es foem smdividval sstems
tOndom memoNy acces
Cemtesy 0999ugates them and them
in the datd )
Users weth the helb
krovioles them to the mdividual
of vsrhaliyation vsng Aybenuisous.
Basically thsuu ayors o memay au pusent,
|- Host mochine mumay
bronides a Corntigusus nmnt shate fas tha Use.
by ibrtealnachene
9 Guest oberating Syotem biyoical mLomay
Kemil
Bus esrted to the vm (viortvalnachne ) byvm
3e buest oberatng Syten viatoal mLmOny
fasented o afplicoth ns by the guest os
Pouocess of Mumoy Viohalgahion ’
Too ky Conetts au Uscd an the ptocess of

ameoncoy to tha Uses with

hoot's þ'ysleal dffent
vrhalFehon ie iyjbenisan cuates
the hutp of same memnory aond puovicles the
VItal Copies of the
to the d{fent useS. tuhenvibas to
Ustd by the
2- shaolow Po_e Table Tt tack o he otate in
kuch thc
cathons o gives
quest dufines the allo Sances .
Ohch he allocathon of
Lmfosmmathon obout he of he s OUIces
ucond
TA bstoviodes he mamy vistual
e. how
allocated to he UseS s.
hove keem C9uated aually.
omackuines
 Alost
Uuest
vn-Vnvm
Ghyest 0s Pybenvso
Golfer cache Vigtval to

Devte chuven ScheclwlaU

Device
Dsuyes
bhyical tand 'ae
lemulated disk
s

levice logiabdik device

Nzl Netok Toteface Cand

NAS- Vetoask Atachd Stoage ovbleng
visdalgaton ts the kocessof
T/o divite the user Vtally
foem host to
ej)
Tlo dleviees (9esonC ol he Ilo
sounces aste csuated
machne
Le vigtal
psovjolud to Hhe vsen.
dond
of I)o davice vigrtaliahion
Taoces
olevites wtth
he I/o
Usen made a guqyuest oN
he Aelb of guest os.
a bud to he
Ae the ea/uests of tho UseH
I/o stack o!of the quest as.
cS.
 buest os uvicd's vasous fouilathes te buffor cochsig ,

.e.to the
Cll he Uajvests doe semt o the host
Visntucl omkine a! the host.

Host aond chucard by the Aysenuisa.

coby of susovaces ae caated
Difount vihvalijed sasd.
hoom he host bile cend

rovided to the lect

diteunt vm cße ceatedl cond
Ubes.
Pslishe- Swlasuber oclel
Rules
Subscouphin
Pblishor Subject Registen sulascuibe.
Chamel Subgiber
Nohfiatoá
Suhseyaby Subsoülben

clieant

ehost
L Roblishn feblistu will boblish thu sENkeschoml
benvices at sem mesages to he
 Oubysuber- Subdoube to a caiegay of mues
3- Chomel Ricenves misages f n bublisAer aonol
murtan subAOubei subscouphion.
I'socess ’ Tl bublishen wants to bublish oony tortentt vsng
to Ghamel ,Ae semds the myiage to the omel using
bublsh Command. As scon as the Cortent is bublishad to
he chemel, ll he scbssubes gets a onohfcahon)
he sgmme dond can check the Cortent ds0.
hu acivihes thct the subsoube com
- Sulosciber caon Bubiube o the chomel
Subscsiber caon nsubibe fotom he Chenel
Sebsiber follous the swles Qomd sbstibton methods
bitoided by he chamnel.
Aelvotages loo Cojling on the blistr' end
-Redvced Cognthve lo ad on the subscibets
Sya-seherchon of Concems
- Tom bstoved testablty
5. Tomjstovecd Stcwsty.
DIsachaoriaze > Inflwiblity of data Send by the jablishun
chaonging he fomat of he mesag e s not an eaiy task. Tt
stayunaus aftnmahon of all the bulolishurs.
Tastabiley of celivery
the subsouber
fublioher does not Have the hetfect soha cl
he
bometis Umwateol ost palst subsubers caon he
sttcton that stops a buces on achvy prom kaogud
Bottlenks>A
Somtims load sges Can slow dowen mesage
subscoiben gets a selks in the susbonse
btding an
Am
 Vbrlal dlsasjes sutovery is a ghe of disaster suDve
hat tsitally mvolves sahlitcdhon dnd eables a user to
fail over to vibrhalizd woklonds
Fon the oost efluent viual disasten uoveny,
csgondscthon ahovld coby vm woskloacs ofß-site on
Rsl'tahon essehaly moks a sual stione
d sugulan bas's stamgthmmg DR
a sebatrate tocahon ,
Coby of vma tin
tei'saste suLovey )
Bemufts of vistal Disaster Raov eny
Vtualgah mkoovids oribilty in disaster utovey.
Whenevens ate vibrtvalgd ,, thy ate ontatineuzed sosto
Vms ndebenndleont fom he ndoyoj hasdsasu hyskal
does anet neeol the some
fhn cgaouscthon seconolay olkaste
bevers dt he kmay site as at sts
olecovery site.
vibtual diaster Saceveny mclude ease, effereong,
sheed aad byovide hgh oyadlob,lt in the eveant of faile
vÛhdlgahon Aushs ango9sahons mct Rcovery Time
Cbjectves CRTO) aond Recovery foÝtt oyecthves CRPO ) as
súpducach on s done as fouayvennty
Aouayuemty as onecded.
hblecahorm ,Computer, nutoart on oystem Com be
a Hen a9n Unexbected odi'saster, faclve o
lonpanokle event toks Alace

-as muasTud by tiome- htt caon be lost oAter

a ucorey otom a olukaster, filuse o Gomjavghle
eVemt befoe data Loss wil exceed yht s acebable -to
an ogaoni,chen
Vithal oksasten sucoVeny plamming cmd testing >
H ioihval disatten ucovery hloon kas many shnlatbes
oda toudihonal DR Þloon . Aon agaqusethon shotd do
y Decidle cthich systems aond data asue Hhe onaLe couhcal
for gucoen
Docmint couh cal systens dmd data
Gut momagtomantt sphosct fo the DR lam
Comblete a susk assessoneort dand bustness Lmpact nalg's
to outline kossibl gusts and heir footehal kanþats
s Documet btehs anuded fo LiOVery
Defne RTOS cod RPos
Test the þloon.
The cganib cthon shovld sa View aond test s vbrhal
disaster outONeny blan on a agular krodvchon bas)s , esbecaly often
becon made to the Gnnomeet
ny changes hove bhyslcdl
Vibsttvdlzochon will cdecouase he oned fo9
othor date Cespter openaton Rand wae
bevns ad you dont
mosL Vms uans
Moseoven , UsIng hugA
weh Hhe Cost of yeusi dato Centern t
haveto chal
bouJer Consmpton anc tooling syotems
 Bef vinhaliyon ,the cheatry sysem nenags the hmtae
otr vibtalihohon a vbral Logey %longeted betieem he
havdhase and the ohetotorg ystem.
Iute , dafeot oheratog ysiem sch as Aonek,
wirdou)b ca9) easily um on a soame byslcdl omactime.

-thoeae seVeNal clases of m

aychtecoe jonagnely.
The xen achetectuL
Hasddaru vlstaligochon onechaen'son
I- Foll visthalizotion
virheliyatin
> Host basedl viordlijcton
The Yem aychitechte
hem is n ohem soutCe hybevisa koogoom dvelebed hy
Cambstdlye vntsexsty
4 Xem does not loncluole dony dlov ice divey
# ooVloles a omuthausom by wleth a guest os (am hove
di'uct aces to hu physical devices.

konel oond dhpliiahaonb

ahonPhelcaton
Akluocron

osDomain o
Xem wihdaws

Harduae dovces
's Bheeial dloman o Aa ContooL am d
The yem achitechot a7blicathons
quest domaions
demain5 faa
fa vseI
/0 and evenal
olbilty ta callud
"hu quat os, thieth has ConrokDomain U. Doman 0
Domaitn 0, dord the oths au called
is o bivil1geo gvest 0s ofthenXem.
loaded xem bootA wHhavt any fle
Ais frs dugned to
aviloble- Domabs o s
sysem douVeus kung manage dwices
agress hadluae dliuctly oond Domaon O
syboonslbileh es of
one of he
snd mah hadwou swoUNces fonhe
ds to dlbotate
quest domnaurt.
In case ; doma) o tauls hen he ohe
domats U also tail.
 SOAP CSimþle obyct Aces Aotocol) ,

betseen nools It vses XML

Commnnitate thsoug hout

SOAP dllows ksuoces3es to
since batocols
hlatfosmó, Jangages ond operating systeonsplatfs.
aluady stallid on all
Tt ls a bxototol to acess websevibes

SOnp message SoAP messoge

Gordteant
Reavest Servie
cdieont
HResfonse
Rusbrnse
Sevice Boviblor.
Semte Raajwester
Examplu Cedit Cand Cabbliabon)
(obblicahon) )
clieart modele Sen vike kuvion
web
Cudrf Cad,Cw
Sevite njcks the sohP
latout Um be, msoge&enod
and ConvatsMesoge
Wssve olte, Aatto a Common
exprydate. -thatthe abbliaton
Unclrbtemd
Senve
Web
SOAP
Fogmot
aes web- smces Data exehaonge b)o
HiB a bstctocol to
 Sopp Boal'ng blocks
SoAP Evelope
Contains houe bats

XML mSage SoAP Heacv

mSsege. H SOAP mnesage Can be Headu,
daumanit Block
ofmd os on XmL fosmat
Containing Auaden ond booly SoAf Bocdy
emobsulaed Ln he envelohe. The
faot is wthin the body of th
mege Sopp falt
q- Hedcln Thls þewd is mot mordatoy

dnfamation about the obhlohlens.

Cntains -the actul msage thot is betng
3 Boy t witho the booy
tmsmitted · Fatt is (otacl

Contans the stotus af the bplitaton

Fault ’ This bection abol'taton Thes
Contaitns e0US m the
and also obbeat maethan
chtiondl- Tt stold not
beton is also
Once an q SoApmeysoge
Acvntages of Sopp

bacause tt s basd on xmL

 - SoAP Was deaimed o be o5 and platform tdifendait
top of HT7P whch is Lnstlleo
9. SoAp is many vsed ton web-smtes onol
AHpliathon kxogomrnng Tostefaces CArIa).

wsDL Cweb Sentes bescsubtion Longuag e)

G- Uses
dotomunts ohett is easy to undostand.
for wauting eay
Disod vem ages
xmL and otten fumats au gnot
x Only Sutborts CJovasubt Object Notehon')
BJbbosted socth as JsoN
Hs basedl om contract so tight lobling eaists
betsee clieont qond abblitaton.
+ Arytmc he can be chenge n Seven Sile Cantnc
SoAP kovides wide omge of date imchedong
test, mbes, dotes cmd bnany latg.

setose Combacd to.Jso.

 ilty lond
nicationg.
ons
-lvel buse ohetahons
L CRUD
ulding ahhlcatms mblex ahplicahens
buldi Sostahle
fo
et. WSDL
Steteless 01 moclel serVes
ehsorotocel clieont Sydteles a
SOAP fustl eute beCam
femat ony foomt
dota ony Ube
fo techmolo9 PUT,091 DELEG(bE1,PoST,
ootocal
> omy Use methods HTTp
t follows
fomat dada staute any
sts i
Uses follod
asXmL CIthitechylcloesnt REST
AI REST
veb RESTbetween
vs Oifene
 REST (Rssenatonl State Genafer )
based kogrrmoming Jonterface
KEST ARI io a web
fonom REsT avchttectuet sle . the p
ay web
that anchitectuef bloing
rvble om
of REST Is to kroniole
be Ca Mes by yoou'ous cleant3
sevlees thoct Can Ohblcaons .
web,mobile e oeskto Stndand
based om Hrr whick
Grmnnoneaton on the nternt
ksoto tol UsAd fnon by olue
om the REST bleontfed
Each soUSILe set)N n
Locata ') and susonse
URL CUnifon Rsace
Wotaton ) o XML CExtegnsi ble
JsoM CDovg Scsubt obect
Donb longuage ) fumot
The esscotel featse o REST I6 thot
btateless clientseve noolel 1! meggns thot aeNe
stre any tonfematon dkout the cient
does nt segvest (onte)
beteen eavests onstead eac
State
dinfanthon seausud by he seven to
2 eesany
Jococess the seavest.
Thes anchiteche mrakes REST API salable 4
easy to matintan
When to Vse REST API
REST APIs ae am eycelliont choite them bulelorg
&
veb sebes thect seaybe a stotteless, sale blo
 easy to nara'sn aLAitecuse - TA's Aolal fon bucling
obblitaions that suayued CRUD obeatlons Svch as
(Couating , aoding iuholbting ore dbshng date )
REST API b dlso sutable fa buteling
ahplltcchons that
buch as choct applicathors ( fta mesemgen,
pthnee
googleduo ete) and staueming Uvices ( epli
web ArI Web Ar ls bstoocly tem thet enombnses
all tyhes of Aris hat cam be acesed ovey
the otent. Tt ioncloles REST ARI SoA P et. ond
rany oten -ghs of Arzh. The frinry obose of web
Art is to koovde q blaltoamn ndaperdeat sortenface
that ton be ysed ay VowcUs Clivnts inchell'ng web.
moble cd olestop apblebatios .
Web Arz Uses citfet rotocols sinclcing
H7TPS and ttc. to ComUbate between the
HTTe,
sheiho
Clients omd severs . web ARI doesnt follow a
athite cte 07 stucte hstead t Cam be olegn Usg
Ory tectnalogy o anthiecha depending om the
Seqsunmesnts,
One of the kuy featnL of the web PPI.
is thect t keovisles llrible sotesface voed ay
Yovubvs liests ond #allow5 dlrvelopes to eyb0se
Vauous fynhonalities of the qfhltation ,ibnlaloy
 (RUD oheratons , authanhchien authai'zathon ete and to
mony cths. hi's mokLs Wob Ap1 powenful tool
Complex obplitation hot sugie a lot of
butlolin g d defervont Sstens
Jntegratiom onol Commujeation between
WAm to vse a Web ArE ’
bouoenfu tool o buaing Comblax
Web HPI is a witth oiMeent
othlicotics that staqute ioneychien eble
techraleges. web Aer foovibls
teoss omd -the sejuscernntsof
sy con be wstome to meet olilatons
tinterface. that web, mncb1 le L csttob
va°cus clients ntling

otheugaton ond suity.

outheaticchon , Access Prototal)
(Simple obyect
SoPPPrr ’
qhhlicchons SoPP APz
between ditetmt fallows Sonp
krogmonmgAterface thot
stuehoucl dot
based bupose of SonP isto
ists web cel . The bstmmory ahblikatins
meaging ktolo exchomgc dlak bro
wgg to
oronsle stondlauigedþlattosmoon ktegnonpming kavguoge
Kegardloss of he femat fua seadtng ond
gonge of datatyhes
sueiving t krovtds widle
Sdeulg deta Jata ond dates nd biray dota SoHp
foclucling tot, mombers, anclvolng
omifevbg Jsotoel
also sbo9ts mtiple Betocol'y
and FTPC
HrTe, Smf CSinhle Mau'l Tronsfen
Fle Thonsfer Brctotal). exchngmg mesages
SopP olufnes a set Ules f
wsDL (web
blw ahplitatens. Thus swles au dlifmed Ýn
beites bescupton Lomguoge) .
 Wath sbeufes he famatt of SoPP mesoge ond
Oherahons that coy be benfemed on t.
Anothe
seCUity muchonisms Lmcldong
sbort fo9 achremced
befuseeon dhpucotons
thct docte eyhonge
feats emsUL neUhosuged
accessed by
con mot be
Is se CUse ond
User

ofplecatens hot igu

bulldng
TI (6 vsed to suliable exchorgng
amol method of
a highly beuseahblcahons.
datg beoeeon ofbblcah ons thdt
eamterkuse 's
TA b slahle busines log'
cata stuctuss and
gua,use Complex that sugu're
ahplcottns
TA is suttable fo
eniyhtion
d'_alal syeihsus one
ike an eNelobe hele RuST Iis gust
SoAf is ond caobert to seand
Cotainly aahostcand is faster
abootard Coutd sh be w91g hbedl wthig
on eo velobe. bod t
thon envelobe eelobe
thing else, even an hile am
bon ouada bostcad too
You Cam gust
stehs, Jike oheming o Unwnaptng
toks a few esta
to qcess hot's tside.
 Veb Senvies (ws ) ayd Senvie Ou'enled AchuteciL (SOh)
CH gelated but disnt Concebts neb Senv'ces cot a
wey f
ommUni catng bedween diffoud oofhoae sysleams over
he cntemt
Thuy voe stondaized kofo ols , such as HrTP omd
XML, to exchange musageh . Web Sevices con lbe vsed
fon d vaucy of buyosts , svch s sendng data
between difeunt dcters to a datbse

befesming a sheife tomjwtathion.

Cothtechual boen that focobeS on baoktng a ytem
wsablu Cemponemts called
clowon oto smalln , ethn systems.
fhese sevibes con be Used by
setes. web
qnd ConLoymmunutate weth each other vsmg
systeons thot ae
Useol to Guate
often ondl matatnoble
plosble,scalable
sevices aste away of
web
Ty bommaony osteons , hlle
betieem ouiheunt
Comntitathng hat focuses
oUtChetecteol bote ,teUsOhle
smallwr
systean down oto
d
Conmjoonemts.