CSE 423 Lecture 4
CSE 423 Lecture 4
Security is an obvious threshold question, if the cloud When the user is going to migrate with the outsource
is not secure, enterprises will not consider migrating providers, then the service level agreements and its
to it fearing their sensitive data will be tampered. For terms are thoroughly checked. While the whole idea
eg Users must ensure that they understand the behind cloud computing is to propose a
underlying infrastructure of the cloud to which they standardized, multi-tenant infrastructure, cloud
migrate from their clients and must also advise clients vendors may not offer the same level of custom
to include security in their cloud SLAs and terms of SLAs as IT managers
service
TECHNICAL INTEGRATION THE BUSINESS VIEW
Most firms that migrate to the cloud environment When the user is going to migrate with the outsource
in a hybrid model, are keeping certain key providers, then the service level agreements and its
elements of their infrastructure in-house and terms are thoroughly checked. While the whole idea
under their direct control, while outsourcing less behind cloud computing is to propose a standardized,
susceptible or core components. Integrating multi-tenant infrastructure, cloud vendors may not offer
internal and external infrastructures can be a the same level of custom SLAs as IT managers
technical concern.
Seven step
migration model
Each of these components must be able to interact with one another and
other parts of the system. Apart from some basic components, each type of
middleware needs a specific component. For example, a database middleware
needs a database manager component.
● Common messaging framework
Components Middleware requires messaging
services to communicate with
in middleware services, applications, and
platforms. Most of these
● Middleware management
frameworks rely on existing
console
standards such as simple object
This console provides an
access protocol (SOAP),
overview of events and
representational state transfer
activities, transactions,
(REST), or Javascript object
configuration management, and
notation (JSON).
contract rules.
● Platform interface
Middleware needs to work
across multiple platforms,
irrespective of where it
resides. This is the interface
that is in direct contact with
the backend servers.
Need of
cloud
middleware
Configure and control Secure connections and
connections and data transfer
integrations
Based on information in a client
Middleware typically
or front-end application establishes a secure
request, middleware can connection from the front-
customize the response from the end application to back-end
back-end application or service. data sources using Transport
In a retailer's ecommerce Layer Security (TSL) or
application, middleware
another network security
application logic can sort
product search results from a
protocol. And it can provide
back-end inventory database by authentication capabilities,
nearest store location, based on challenging front-end
the IP address or location application requests for
information in the HTTP request credentials (username and
header. password) or digital
certificates.
Manage traffic
dynamically across
distributed systems
When application traffic
spikes, enterprise
middleware can scale to
distribute client requests
across multiple servers, on
premises or in the cloud.
And concurrent processing
capabilities can prevent
problems when multiple
clients try to access the
same back-end data source
simultaneously.
Quality of service- It is a challenge to
issues in Cloud implement QoS in cloud computing
applications. There are
Quality of Service refers to the many techniques to provide
ability of networks to attain quality of service to the cloud
maximum bandwidth and handle applications. Scheduling,
other network elements admission control and dynamic
like latency, error rate and resource provisioning are some
uptime. Quality of Service techniques used to achieve
include the management of other that goal.
networks resource by
allocating priorities to
specific type of data (audio,
video
and file).
CHALLENGES
Scheduling:
Cloud service scheduling categorized into two categories:
user level and system level.
At user level scheduling deals with problems raised by service
providing between both service provider and customer. Market based and
auction based schedulers are fit for ruling the supply and demand of cloud
resources. Market based resource allocation is powerful in cloud computing
environment where resources are handed over to user as a service.