KGiSL Institute of Technology

(Approved by AICTE, New Delhi; Affiliated to Anna University, Chennai)

Recognized by UGC, Accredited by NBA (IT)
365, KGiSL Campus, Thudiyalur Road, Saravanampatti, Coimbatore – 641035.

Department of Computer Science and Engineering

Name of the Faculty : Ms. T.N.Aruna

Subject Name & Code : CS8791/ Cloud Computing

Branch & Department : Computer Science and Engineering

Year & Semester : IV / VII

Academic Year :2023-24

CS8791/CC/IVCSE/VIISEM/KG-KiTE
 Course Outcome

CO 1 Explain the fundamentals of Cloud Computing.K2 LEVEL

CS8791/CC/IVCSE/VIISEM/KG-KiTE
Syllabus
UNIT I INTRODUCTION
Introduction to Cloud Computing – Definition of Cloud – Evolution
of Cloud Computing –Underlying Principles of Parallel and
Distributed Computing – Cloud Characteristics – Elasticity in Cloud
– On Demand Provisioning

CS8791/CC/IVCSE/VIISEM/KG-KiTE
 Architectural Styles for
Distributed Computing

• We organize the architectural styles into two major classes:

● Software architectural styles
● System architectural styles

CS8791/CC/IVCSE/VIISEM/KG-KiTE
 System Architectural Styles
(Client-Server)
• The client-server model features two major components:
 Server
 Client

• These two components interact with each other through a network connection by using a given

protocol.

• Communication is unidirectional

• Thin-client Model: The load of data processing and transformation is put on the server side

• Fat-client Model: The client component is also responsible for processing and transforming the

data before returning it back to the user. Server is lightweight-->Managing the accessed data

CS8791/CC/IVCSE/VIISEM/KG-KiTE
Client Server Model

CS8791/CC/IVCSE/VIISEM/KG-KiTE
 Two-tier Architecture

• The client is responsible for the presentation tier by providing a user

interface
• The server concentrates the application logic and the data store into a
single tier.
• This architecture is suitable for systems of limited size and suffers from
scalability issues.
• Limitation in dimension of the data to maintain, manage, and access

7
 Three-tier Architecture/N-tier Architecture
• The three-tier architecture separates the presentation of data, the
application logic, and the data storage into three tiers.

• More scalable

• More complex to understand and manage

• Eg: medium-size Web application that relies on a relational

database management system for storing its data.

8
 Peer-to-Peer
•
All the components, called peers, play the same role and incorporate
both the client and server capabilities of the previous model.
• Each peer acts as a server when it processes requests from other
peers and as a client when it issues requests to other peers.
Eg: file sharing applications such as Gnutella, BitTorrent, and Kazaa

9
Peer-to-Peer model

10
 Models for Inter-Process Communication

1. Message-based Communication:
The entities exchanging information explicitly encode, in the form of
message, the data to be exchanged.

2. Remote Procedure Call (RPC):

A remote process hosts a server component, thus allowing client
processes to request the invocation of methods and returns the result
of the execution.

11
 3.Distributed Objects
• Each process registers a set of interfaces that are accessible remotely.
• Client processes can request a pointer to these interfaces and invoke the
methods available through them.
• The communication between the caller and the remote process is made
through messages.
• Stateless by design
• Eg: Common Object Request Broker Architecture (CORBA),
Component Object Model (COM, DCOM and COM+), Java Remote
Method Invocation (RMI ), and .NET Remoting.

12
 4.Distributed Agents and Active Objects

•Objects have their own control thread, which allows them to carry out
their activity.

These models often make explicit use of messages to trigger the

•

execution of methods and a more complex semantics is attached to the

messages.

13
 5.Web Services

• Implementation of the RPC concept over the HTTP transport

protocol.
• A Web service is exposed as a remote object hosted in a Web server.
• Method invocations are transformed in HTTP requests using specific
protocol such as SOAP (Simple Object Access Protocol ) or REST
(REpresentational State Transfer).

14
 Models for Message-based Communication
Point-to-Point Message Model:
•Each message is sent from one component to another.
•We have a direct addressing to identify the message receiver.
•It is necessary to know the location or how to address another
component in the system.
Two major sub-categories:
1.Direct communication: The message is sent directly to the
receiver and processed at the time of reception.
2.Queue-based communication: The receiver maintains a
message queue where the messages received are placed for later
processing. 15
 Publish-Subscribe Message Model
• Based on notification among components.

• Publisher provides facilities for the latter to register its interest in a

specific topic or event.

• Specific conditions holding true on the publisher side can trigger the
creation of messages which are attached to a specific event.

• This message will be available to all the subscribers that registered

for the corresponding event.

16
 Push & Pull Strategy
Push Strategy:
•It is the responsibility of the publisher to notify all the subscribers, for

example, with a method invocation.

Pull Strategy:
•The publisher simply makes available the message for a specific event.

•
It is the responsibility of the subscribers to check whether there are
messages on the events that are registered.

17
 Request-Reply Message Model

• For each of the message sent by a process, there is a reply.

• Does not focus on the number of the components involved in the

communication.

18
 Why it is required?

• With the increased use of computers , Scientists face two crucial issues
today

• Processing has to be done faster like never before

• Large or complex computation problems need to be solved

UNIT-I CLOUD COMPUTING 19

 Architecture Concepts

Von Neumann Architecture🡪 comprised of four main components

•Memory Unit
•Control Unit
•Arithmetic Logic Unit
•Input/Output Unit

UNIT-I CLOUD COMPUTING 20

 Types of Distributed Systems

• Distributed Computing Systems

• Distributed Information Systems
• Distributed Pervasive Systems

UNIT-I CLOUD COMPUTING 21

 Examples of Distributed Systems

• Local Area Network and Intranet

• Database Management System
• Automatic Teller Machine Network
• Internet/ World-Wide Web
• Mobile and Ubiquitous Computing

UNIT-I CLOUD COMPUTING 22

 Common Characteristics
• Security
• Openness
• Scalability
• Failure Handling
• Concurrency
• Transparency
• Heterogeneity

UNIT-I CLOUD COMPUTING 23

 Basic Design Issues

• Naming
• Communication
• Software structure
• System architecture
• Workload allocation
• Consistency maintenance

UNIT-I CLOUD COMPUTING 24

 Advantages & Disadvantages
Advantages
•Sharing Data
•Autonomy
•Availability
Disadvantages
•Software Development Cost
•Greater Potential for Bugs
•Increased Processing Overhead

UNIT-I CLOUD COMPUTING 25

 Time To Think (T2T)
What is batch sequential style? (BT Level- Remember)
a) In batch sequential components are independent programs
b) Assumptions is that each step runs to completion before the
next step starts
c) All of the mentioned
d) None of the mentioned

Ans: C

CS8791/CC/IVCSE/VIISEM/KG-KiTE
 Time To Think (T2T)
In which of the following style new clients can be added easily? (BT
Level- Remember)
a) Data Flow Architecture
b) Call and Return Architecture
c) Data Centered Architectures
d) None of the mentioned
Ans: C

CS8791/CC/IVCSE/VIISEM/KG-KiTE