Scribd
Upload
34 views

Mirpur University of Science and Technology (Must), Mirpur Deparment Computer Science Information Technology

This document discusses different types of distributed systems. It describes transaction processing systems and their ACID properties of atomicity, consistency, isolation, and durability. It discusses transaction processing monitors and enterprise application integration using remote procedure calls and message-oriented middleware. It also describes distributed pervasive systems, home systems, and electronic healthcare systems, noting questions around data storage, alerts, security and robust monitoring for the latter.

Uploaded by

sobia sher
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
34 views

Mirpur University of Science and Technology (Must), Mirpur Deparment Computer Science Information Technology

This document discusses different types of distributed systems. It describes transaction processing systems and their ACID properties of atomicity, consistency, isolation, and durability. It discusses transaction processing monitors and enterprise application integration using remote procedure calls and message-oriented middleware. It also describes distributed pervasive systems, home systems, and electronic healthcare systems, noting questions around data storage, alerts, security and robust monitoring for the latter.

Uploaded by

sobia sher
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

MIRPUR UNIVERSITY OF SCIENCE AND TECHNOLOGY (MUST), MIRPUR

DEPARMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY


Distributed Computing
BIT-3606

Lecture [4] : Types of Distributed Systems(b)

Sobia Sher
(Lecturer)
Today’s Agenda

We will discuss following topics:


• Transaction Processing Systems
• Distributed Pervasive Systems
• Home Systems
• Electronic Health Care Systems

Distributed Computing 3
Transaction Processing Systems
RPC, procedure calls to remote servers, are often encapsulated in a
transaction, leading to what is known as a transactional RPC.

Figure 1. Example primitives for transactions.

Distributed Computing 4
Transaction Processing Systems

• BEGIN – TRANACTION AND END-TRANSACTION


are used to delimit the scope of a transaction.
• The operations between them form the body of the
transaction.
• The characteristic feature of a transaction is either all of
these operations are executed or none are executed.

Distributed Computing 5
Transaction Processing Systems –
ACID
Characteristic properties of transactions:
• Atomic: To the outside world, the transaction happens
indivisibly.
• Consistent: The transaction does not violate system
invariants.
• Isolated or serializable: Concurrent transactions do not
interfere with each other.
• Durable: Once a transaction commits, the changes are
permanent.

Distributed Computing 6
Transaction Processing Systems

Figure 2. A nested transaction

Distributed Computing 7
Transaction processing monitor or TP monitor
 Its main task was to allow an application to access multiple server/databases by offering it a transactional
programming model as shown in the following figure.

Figure 3: the role of a TP monitor in distributed systems

Distributed Computing 8
Enterprise Application Integration(EAI)
 Remote procedure calls (RPC)
• Send a request to another application component by doing a local procedure
call
 Remote method invocations (RMI)
• It operates on objects instead of applications
o Disadvantage
• Caller and callee need to be up and running at the time of communication
• Tight coupling
 Message oriented middleware(MOM)
• Here applications simply send messages to logical contact points, often
described by means of a subject.
• Publish/subscribe systems form an important and expanding class of distributed
systems.
Distributed Computing 9
Enterprise Application Integration

Figure 4. Middleware as a communication facilitator in enterprise application integration.

Distributed Computing 10
Distributed Pervasive Systems
 Requirements for pervasive systems

• Embrace contextual changes.


• A device must be aware of the fact that its environment may change
all the time
• Encourage ad hoc composition.
• Different ways by different users
• Recognize sharing as the default.
• Access (and possibly provide) information

Distributed Computing 11
Home Systems
 Typical consumer electronics such as
• TVs, audio and video equipment, gaming
devices, (smart) phones, PDAs, and other
personal wearable's into a single system
 Personal space
• Agenda, family photo’s, a diary, music and
videos, etc.

Distributed Computing 12
Electronic Health Care Systems
 Questions to be addressed for health care systems:
Where and how should monitored data be stored?

How can we prevent loss of crucial data?

What infrastructure is needed to generate and propagate alerts?

How can physicians provide online feedback?

How can extreme robustness of the monitoring system be


realized?

What are the security issues and how can the proper policies be
enforced?

Distributed Computing 13
Electronic Health Care Systems

Figure 5. Monitoring a person in a pervasive electronic health care system, using (a) a
local hub or (b) a continuous wireless connection.

Distributed Computing 14
Today’s Reading and Next Lecture

• (Distributed Systems: Principles and Paradigms,


Andrew S. Tanenbaum and Maarten van Steen.
Prentice-Hall, 2002.) chap 1, section 1.3
• Start solving the exercises at the end of each
chapter section!

• Please read 2.1 in preparation for the next lecture

Distributed Computing 15
THANKS

You might also like