Unit-3 (Part-I
Unit-3 (Part-I
Figure 5. The internetworking architecture of a private cloud. The physical IT resources that
constitute the cloud are located and managed within the organization
3.Technical and Business Considerations:
Figure 8. The common components of a data center working together to provide virtualized IT resources supported by
physical IT resources.
Data Center Technology
2.Standardization and Modularity:
•Modularity and standardization are key requirements for reducing investment and operational costs
as they enable economies of scale for the procurement, acquisition, deployment, operation, and
maintenance processes.
•Consolidated IT resources can serve different systems and be shared among different cloud consumers
3.Automation:
•Data centers have specialized platforms that automate tasks like provisioning, configuration,
•Advances in data center management platforms and tools leverage autonomic computing technologies
7.Facilities:
•Facilities are custom-designed locations that are outfitted with specialized computing, storage,
and network equipment These facilities have several functional layout areas, as well as various
power supplies, cabling, and environmental control stations that regulate heating, ventilation, air
conditioning, fire protection, and other related subsystems.
Data Center Technology
8.Computing Hardware:
•Data centers is often executed by standardized commodity servers that have substantial computing
power and storage capacity.
•Rackmount form factor server design composed of standardized racks with interconnects for power,
network, and internal cooling.
•support for different hardware processing architectures, such as x86-32bits, x86-64, and RISC
•Each tenant has its own view of the application that it uses, administers and
customizes as a dedicated instance of the software while remaining unaware of
other tenants that are using the same application.
•Multitenant applications ensure that tenants do not have access to data and
configuration information that is not their own.
2.Business Process: Tenants can customize the rules, logic, and workflows of
the business processes that are implemented in the application.
3.Data Model: Tenants can extend the data schema of the application to include,
exclude, or rename fields in the application data structures.
4.Access Control: Tenants can independently control the access rights for users
and groups.
Multitenant Technology
Characteristics:
•Usage Isolation
•Data Security
•Recovery
•Application Upgrades
•Scalability
•Metered Usage
•Data Tier Isolation
Multitenant Technology
Common Characteristics of multitenant application include :
•Usage Isolation: The usage behavior of one tenant does not affect the application
availability and performance of other tenants
•Data Security: Tenants cannot access data that belongs to other tenants
•Recovery: Backup and restore procedures are separately executed for the data of each tenant
•Application Upgrades: Tenants are not negatively affected by the synchronous upgrading of
shared software artifacts.
• Scalability: The application can scale to accommodate increases in usage by existing
tenants and / or increases in the number of tenants
• Metered Usage : Tenants are charged only for the application processing and features that
are actually consumed
•Data Tier Isolation: Tenants can have individual databases, tables, and/or schemas isolated
from other tenants. Alternatively, databases, tables, and/or schemas can be designed to be
intentionally shared by tenants
Multitenant Technology
Multitenancy is sometimes mistaken for virtualization because the concept of
multiple tenants is similar to the concept of virtualized instances.
The differences lie in what is multiplied within a physical server acting as host.
•With virtualization: Multiple virtual copies of the server environment can be
hosted by a single physical server. Each copy can be provided to different users,
can be configured independently, and can contain its own operating systems and
applications.
•With multitenancy: A physical or virtual server hosting an application is
designed to allow usage by multiple different users. Each user feels as though they
have exclusive usage of the application.
Service Technology
Service technology is a keystone foundation of cloud computing that formed the basis of
the “as-a-service” cloud delivery models.
Web Services:
•Web Service Description Language (WSDL): This markup language is used to create a
WSDL definition that defines the application programming interface (API) of a Web
service.
•XML Schema Definition Language (XML Schema): Messages exchanged by Web
services must be expresses using XML.
•SOAP: Familiarly known as the Simple Object Access Protocol, this standard defines a
common messaging format used for request and response messages exchanged by Web
services.
•Universal Description, Discovery, and Integration (UDDI): This standard regulates
service registries in which WSDL definitions can be published as part of a service catalog
for discovery purposes.
Service Technology
ReST (Representational State Transfer) Services
ReST services are designed according to a set of constraints that shape the service
architecture to emulate the properties of the World Wide Web.
ReST services do not have individual technical interfaces but instead share a common
technical interface that is known as the uniform contract, which is typically established via the use of
HTTP methods.
•Client-Server
•Stateless
•Cache
•Interface/Uniform Contract
•Layered System
•Code-On-Demand
Service Technology
Service Agents
Service agents are event-driven programs designed to intercept messages at runtime.
There are two types of service agents:
•Active service agents perform an action upon intercepting and reading the contents of a message
•Passive service agents, on the other hand, do not change message contents.
Service Middleware
Middleware platforms that evolved from messaging-oriented middleware (MOM) platforms used
primarily to facilitate integration, to sophisticated service middleware platforms designed to
accommodate complex service compositions.
Two most common types of middleware platforms relevant to services computing are:
•Enterprise service bus(ESB): encompass a range of intermediary processing features including service
brokerage routing and message queuing.
•Orchestration platform: environments are designed to host and execute workflow logic that drives the
runtime composition of services.