FUNDAMENTAL

CLOUD
ARCHITECTUR
E

1
FUNDAMENTAL CLOUD ARCHITECTURE
1. Workload Distribution Architecture

2. Resource Pooling Architecture

3. Dynamic Scalability Architecture

4. . Elastic Resource Capacity Architecture

5. . Service Load Balancing Architecture

6. . Cloud Bursting Architecture

7. . Elastic Disk Provisioning Architecture

8. . Redundant Storage Architecture

9. Other Mechanisms

2
FUNDAMENTAL CLOUD ARCHITECTURE
1. Workload Distribution Architecture

• Horizontally scaled
• Load balancing algorithm and runtime logic manage the workload.
• Distribute workload evenly among available IT resources.
• Reduced both IT resources over-utilization and under-utilization
• Load balancing systems applied to specific IT resources usually produce specialized
variations of this architecture that incorporate aspects of load balancing , such as

1.The Service load balancing architecture

2.The load balanced virtual server architecture

3. 2.The load balanced virtual switch architecture

3
4
2. Resource Pooling Architecture

• Identical IT resources are grouped and maintained by a system.

• Multiple pools can be created for specific cloud consumers or applications.

•A hierarchical structure can be established to form parent, sibling, and

nested pools in order to facilitate the organization.

• Nested Pools - larger pools are divided into smaller pools that individually
group the same type of IT resources together

5
• Dedicated Pools - can be created for each type of IT resource and individual pools
can be grouped into a larger pool, in which case each individual pool becomes a
sub-pool.

6
Sibling resource pool

7
Nested pool model

8
3.Dynamic Scalability Architecture

• Based on a system of predefined scaling conditions

that trigger the dynamic allocation of IT resources from
resource pools.Dynamic allocation enables variable utilisation by
Usage demand fluctuations , since unnecessary IT resources are
efficiently reclaimed without requiring manual interaction.

• Automated scaling listener is configured with workload thresholds

• Determines how many additional IT resources can be dynamically
provided, based on the terms of a given cloud consumer’s
provisioning contract.

9
Types
• Dynamic Horizontal Scaling
• IT resource instances are scaled out and in to handle fluctuating workloads.

• Automatic scaling listener monitors requests and signals resource replication

to initiate IT resource duplication, as per requirements and permissions.

• Dynamic Vertical Scaling

• IT resource instances are scaled up and down when there is a need to adjust
the processing capacity of a single IT resource.

• Dynamic Relocation
• The IT resource is relocated to a host with more capacity.

10
Cloud service consumers are sending requests to a cloud service (1). The automated
scaling listener monitors the cloud service to determine if predefined capacity thresholds
are being exceeded

11
12
13
4. Elastic Resource Capacity Architecture

• Dynamic provisioning of virtual servers, using a system that allocates and

reclaims CPUs and RAM in immediate response to the fluctuating processing.

• Resource pools are used by scaling technology that interacts with the hypervisor
and/ or VIM to retrieve and return CPU and RAM resources at runtime.

14
Paper work

15
5. Service Load Balancing Architecture

• Geared specifically for scaling cloud service implementations.

• Load balancer can be positioned either independent of the cloud services and
their host servers or built-in as part of the application or server’s environment.

16
Workload process is
horizontally scaled

17
18
6. Cloud Bursting Architecture

• Establishes a form of dynamic scaling that scales or “bursts out” on-premise IT

resources into a cloud whenever predefined capacity thresholds have been reached.

• Cloud bursting is a flexible scaling architecture that provides cloud consumers with the
option of using cloud – based IT resources only to meet higher usage commands.

• The foundation of this architectural model is based on the automated scaling

listener and resource replication mechanisms.

• The automated scaling listener determines when to redirect requests to cloud-based IT

resources, and resource replication is used to maintain synchronicity between on-
premise and cloud-based IT resources

19
20
7. Elastic Disk Provisioning Architecture
Cloud consumers are commonly charged for cloud – based storage space
based on fixed –disk storage allocation.

The cloud consumer is billed for using 450GB of storage space after
installing the operating system ,even though the operating system only
requires 15GB of storage space.

21
The below figure demonstrates this by illustrating the scenario in which a cloud
consumer provisions a virtual server with the Windows Server operating system
and three 150 GB hard drives.

22
The System uses the thin – provisioning technology for the dynamic allocation of
storage space , and is further supported by runtime usage monitoring to collect
accurate usage data for billing purposes.
Hypervisor creates additional space to the resources.

23
8. Redundant Storage Architecture

• Introduces a secondary duplicate cloud storage device as part of a failover system

that synchronises its data with the data in the primary cloud storage device.

• A storage service gateway diverts cloud consumer requests to the secondary

device whenever the primary device fails

24
• A logical unit number (LUN) is a logical drive
that represents a partition of a physical drive.

• The storage service gateway is a component that acts as the external interface to cloud
storage services, and is capable of automatically redirecting cloud consumer requests
whenever the location of the requested data has changed

25
• This cloud architecture primarily relies on a storage replication system that keeps the
primary cloud storage device synchronised with its duplicate secondary cloud storage
devices

• Storage replication is a variation of the resource replication mechanisms used to

synchronously or asynchronously replicate data from a primary storage device to a
secondary storage device. It can be used to replicate partial and entire LUNs.

26
9. Other Mechanisms

• AuditMonitor–When distributing runtime workloads, the type and geographical location

of the IT resources that process the data can determine whether monitoring is necessary
to fulfill legal and regulatory requirements.

• CloudUsageMonitor–Various monitors can be involved to carryout runtime workload

tracking and data processing.

• Hypervisor–Workloads between hypervisors and the virtual servers that they host may
require distribution.

• LogicalNetworkPerimeter–The logical network perimeter isolates cloud consumer

network boundaries in relation to how and where workloads are distributed.

• ResourceCluster–Clustered IT resources inactive/active mode are commonly used to

support workload balancing between different cluster nodes.

• ResourceReplication–This mechanism can generate new instances of virtualized IT

resources in response to runtime workload distribution demands.

27