PERANCANGAN DAN PENGEMBANGAN

APLIKASI TERDISTRIBUSI

Agenda :
- Pengantar Sistem Terdistribusi
- Potensi Riset Bidang Sistem Terdistribusi
- Karakteristik Sistem Terdistribusi

Nama
HP

Profil

: Trias Bratakusuma S.E., Ak., M.MSI

: 081 383 502 539

Email

: bratatkr@gmail.com

Office

: Ruang Pengajaran / Dosen Lama

Pokok Bahasan Sistem Terdistribusi :

1. Definisi dan Karakteristik Sistem Terdistribusi
2. Format Data Pertukaran Pesan (XML & JSON)

Pokok
Bahasan

3. SOAP Web Services

4. REST Web Services
5. SOAP Windows Communication Foundation
6. REST Windows Communication Foundation
7. Web API

Pelaksanaan Evaluasi Project Kelompok :

1. Tiap kelompok mengajukan judul dan penjelasan
secara umum project yang akan dibuat. Pengajuan

Evaluasi
Project
Kelompok

judul dibuka mulai minggu ke-4 perkuliahan.

2. Evaluasi rancangan/arsitektur/skema project sistem
terdistribusi dilaksanakan pada Minggu ke-6
perkuliahan.
3. Evaluasi implementasi project aplikasi terdistribusi
dilaksanakan pada Minggu ke-11 & 12 perkuliahan

Komposisi Penilaian :
1. Presensi

: 15%

2. Tugas : 15%

Kontrak
Kuliah

3. Project : 30%
4. UTS
5. UAS

: 20%
: 20%

Aturan Perkuliahan :
Aturan mengenai pakaian dan atributnya mengikuti
peraturan kampus yang berlaku.
Apabila mahasiswa terlambat kehadirannya > 30

Aturan
Perkuliahan

menit, maka mahasiswa tersebut tidak diijinkan

mengikuti perkuliahan*
Apabila dosen terlambat kehadirannya > 30 menit,
maka

kuliah

dikosongkan,

jam

pengganti

diumumkan kemudian*
Plagiarisme Project : Nilai Kelompok = 0

akan

Contoh Kajian Riset :

PENERAPAN XML WEB SERVICE UNTUK SISTEM
DISTRIBUSI BARANG STUDI KASUS :PT. APOTIK PLUS
PALEMBANG

Contoh
Kajian Riset
Sistem
Terdistribusi

PERANCANGAN APLIKASI MOBILE

YOGYAKARTA BERBASIS ANDROID

CITY

DIRECTORY

KEBUTUHAN WEB SERVICE UNTUK SINKRONISASI DATA

ANTAR SISTEM INFORMASI DALAM E-GOV DI PEMKAB
BANTUL YOGYAKARTA
MODELLING XML AND WEB SERVICES MESSAGES WITH
UML

Distributed system as one in which hardware or

software components located at networked computers
communicate and coordinate their actions only by
passing messages. This simple definition covers the

Definisi
Sistem
Terdistribusi

entire range of systems in which networked computers

can usefully be deployed. (Coulouris et al., 2012)

Satu sistem dimana beberapa komputer pada jaringan saling

berkomunikasi, berkoordinasi, dan bekerja sama dengan cara
saling bertukar pesan (Tanenbaum & van Steen, 2007).
Ciri :

Definisi
Sistem
Terdistribusi

Komputer-komputer saling independen

Memiliki memori dan prosesor sendiri
Dihubungkan dalam jaringan komputer
LAN / WAN
Terlihat sebagai satu kesatuan
Komputasi terintegrasi
Dapat diterapkan pada middleware

Jaringan Komputer.

Sistem
Terdistribusi
vs
Jaringan
Komputer

Komputer otonom yang secara eksplisit terlihat (secara

eksplisit teralamati), dengan IP address masing-masing
komputer.
Sistem Terdistribusi.
Keberadaan

beberapa

komputer

otonom

bersifat

setiap

sistem

transparan, sebagai satu kesatuan.

Persamaan

Secara

normal,

terdistribusi mengandalkan layanan yang disediakan

oleh jaringan komputer berbasis TCP/IP

Internet

Radio T ower

Laptop computers

PC T erminals
FDDI Ring

Ilustrasi

Satellite dish

Ethernet connections

Workstation

Servers

Servers

Ilustrasi
Sistem
Terdistribusi
sebagai
Middleware
A distributed system organized as middleware. The middleware layer extends
over multiple machines, and offers each application the same interface.

1. Making resources available (Pemakaian bersama

atas sumber daya)
. The main goal of a distributed system is to make
it easy for the users (and applications) to access

Karakteristi
k Sistem
Terdistribusi

remote resources, and to share them in a

controlled and efficient way.
. Resources can be just about anything, but typical
examples include things like printers, computers,
storage facilities, data, files, Web pages, and
networks.
. Reason : economics

2. Distribution transparency (Transparansi)

. An important goal of a distributed system is to
hide the fact that its processes and resources are
physically distributed across multiple computers.

Karakteristi
k Sistem
Terdistribusi

3. Openness (Keterbukaan)
Open distributed system
Be able to interact with services from other open systems,
irrespective of the underlying environment:

Karakteristi
k Sistem
Terdistribusi

. Systems should conform to well-defined interfaces

. Systems should support portability of applications
. Systems should easily interoperate
Achieving openness
At least make the distributed system independent from
heterogeneity of the underlying environment:
.. Hardware
.. Platforms
.. Languages

Implementing openness

Requires support for different policies :

What level of consistency do we require for client-cached

data?

Karakteristi
k Sistem
Terdistribusi

Which operations do we allow downloaded code to perform?

Which QoS requirements do we adjust in the face of varying

bandwidth?

What level of secrecy do we require for communication?

Implementing openness
Ideally, a distributed system provides only mechanisms :

Allow (dynamic) setting of caching policies

Support different levels of trust for mobile code

Provide adjustable QoS parameters per data stream

Offer different encryption algorithms

4. Scalability (Skalabilitas)
Scalability
At least three components :
. Number of users and/or processes (size scalability)

Karakteristi
k Sistem
Terdistribusi

. Maximum

distance

between

nodes

(geographical

scalability)
. Number of administrative domains (administrative
scalability)
Observation
Most systems account only, to a certain extent, for size
scalability. The (non)solution: powerful servers. Today, the
challenge
scalability.

lies

in

geographical

and

administrative

Scalability Problems
First consider scaling with respect to size. If more users or
resources need to be supported, we are often confronted
with the limitations of centralized services, data, and

Karakteristi
k Sistem
Terdistribusi

algorithms.

Trouble : the server can become a bottleneck as the

number of users and applications grows.
Alternative Solution : Copying the server to several
locations to enhance performance

Techniques for Scaling

A. Hide communication latencies
Avoid waiting for responses; do something else :
. Make use of asynchronous communication

Karakteristi
k Sistem
Terdistribusi

. Have separate handler for incoming response

. Problem: not every application fits this model
B. Distribution
Partition data and computations across multiple
machines :
. Move computations to clients (Java applets)
. Decentralized naming services (DNS)
. Decentralized information systems (WWW)

Techniques for Scaling (Cont)

C. Replication/caching
Make copies of data available at different
machines :

Karakteristi
k Sistem
Terdistribusi

. Replicated file servers and databases

. Mirrored Web sites
. Web caches (in browsers and proxies)
. File caching (at server and client)

Sample :

Karakteristi
k Sistem
Terdistribusi

Figure 1-4. The difference between letting (a) a server or (b) a

client check forms as they are being filled.

False assumptions made by first time developer :

The network is reliable.

Pitfalls
when
Developing
Distributed
Systems

The network is secure.

The network is homogeneous.
The topology does not change.
Latency is zero.
Bandwidth is infinite.
Transport cost is zero.
There is one administrator.

Example : 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?

Example

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?

Example : Electronic Health Care Systems

TYPES OF
DISTRIBUTE
D SYSTEMS
. Figure 1-12. Monitoring a person in a pervasive electronic health care system, using :
. (a) a local hub or
. (b) a continuous wireless connection.

1. Heterogeneity
2. Openness
3. Security

CHALLENGE
S

4. Scalability
5. Failure handling
6. Concurrency