SlideShare a Scribd company logo
INTRODUCTION:-

          In the term distributed computing, the word distributed means spread out across
space. Thus, distributed computing is an activity performed on a spatially distributed
system.
          A distributed system consists of collection of autonomous computers, connected
through a network and distributed operating system software, which enables computers to
coordinate their activities and to share the resources of the system - hardware, software
and data, so that users perceive the system as a single, integrated computing facility.




                                             16
(Figure 1-Distributed Computing)


         These networked computers may be in the same room, same campus, same
country, or in different continents. A distributed system may have a common goal, such
as solving a large computational problem. Alternatively, each computer may have its own




                                          16
user with individual needs, and the purpose of the distributed system is to coordinate the
use of shared resources or provide communication services to the users.


Rise of Distributed Computing:-
    Computer hardware prices are falling and power increasing.
    Network connectivity is increasing.
    Everyone is connected with fat pipes.
    It is easy to connect hardware together.
    Combination of cheap processors often more
    Cost-effective than one expensive fast system.
       Flexibility to add according to needs.
       Potential increase of reliability.
       Sharing of resources.


Characteristics of Distributed Computing:-
       Six key characteristics are primarily responsible for the usefulness of distributed
system. They are resource sharing, openness, concurrency, scalability, fault tolerance and
transparency. It should be emphasized that they are not automatic consequences of
distribution; system must be carefully designed in order to ensure that they are achieved.


      Resource Sharing:-
        Resource sharing is the ability to use any hardware, software or data anywhere in
the system. Resources in a distributed system, unlike the centralized one, are physically
encapsulated within one of the computers and can only be accessed from others by
communication. It is the resource manager to offers a communication interface enabling
the resource be accessed, manipulated and updated reliability and consistently. There are
mainly two kinds of model resource managers: client/server model and the object-based
model. Object Management Group uses the latter one in CORBA, in which any resource




                                             16
is treated as an object that encapsulates the resource by means of operations that users
can invoke.


      Openness:-
        Openness is concerned with extensions and improvements of distributed systems.
New components have to be integrated with existing components so that the added
functionality becomes accessible from the distributed system as a whole. Hence, the static
and dynamic properties of services provided by components have to be published in
detailed interfaces.



      Concurrency:-
          Concurrency arises naturally in distributed systems from the separate activities
of users, the independence of resources and the location of server processes in separate
computers. Components in distributed systems are executed in concurrent processes.
These processes may access the same resource concurrently. Thus the server process
must coordinate their actions to ensure system integrity and data integrity.


      Scalability:-
          Scalability concerns the ease of the increasing the scale of the system (e.g. the
number of processor) so as to accommodate more users and/or to improve the
corresponding responsiveness of the system. Ideally, components should not need to be
changed when the scale of a system increases.


      Fault tolerance:-
            Fault tolerance cares the reliability of the system so that in case of failure of
hardware, software or network, the system continues to operate properly, without
significantly degrading the performance of the system. It may be achieved by recovery
(software) and redundancy (both software and hardware).




                                             16
    Transparency:-
            Transparency hides the complexity of the distributed systems to the users and
application programmers. They can perceive it as a whole rather than a collection of
cooperating components in order to reduce the difficulties in design and in operation.
This characteristic is orthogonal to the others. There are many aspects of transparency,
including access transparency, location transparency, concurrency transparency,
replication transparency, failure transparency, migration transparency, performance
transparency and scaling transparency.




 Distributed Computing Architecture:-
       Various hardware and software architectures are used for distributed computing. At
a lower level, it is necessary to interconnect multiple CPUs with some sort of network,
regardless of whether that network is printed onto a circuit board or made up of loosely-
coupled     devices    and     cables.   At   a    higher   level,   it   is   necessary    to
interconnect processes running on those CPUs with some sort of communication system.

          Distributed programming typically falls into one of several basic architectures or
categories: Client-server, 3-tier architecture, N-tier architecture, Distributed objects, loose
coupling, or tight coupling.


       Client-server:-
          Smart client code contacts the server for data, then formats and displays it to the
        user. Input at the client is committed back to the server when it represents a
        permanent change.




                                              16
   3-tier architecture :-
    Three tier systems move the client intelligence to a middle tier so that stateless
    clients can be used. This simplifies application deployment. Most web
    applications are 3-Tier.


   N-tier architecture:-
      N-Tier refers typically to web applications which further forward their requests
    to other enterprise services. This type of application is the one most responsible
    for the success of application servers.


   Tightly coupled (clustered):-
        Tightly coupled architecture refers typically to a cluster of machines that
    closely work together, running a shared process in parallel. The task is subdivided
    in parts that are made individually by each one and then put back together to
    make the final result.


   Peer-to-peer:-
      Peer-to-peer is an architecture where there is no special machine or machines
    that provide a service or manage the network resources. Instead all responsibilities
    are uniformly divided among all machines, known as peers. Peers can serve both
    as clients and servers.


   Space based :-
       Space based refers to an infrastructure that creates the illusion (virtualization)
    of one single address-space. Data are transparently replicated according to
    application needs. Decoupling in time, space and reference is achieved.




                                         16
Another basic aspect of distributed computing architecture is the method of
communicating and coordinating work among concurrent processes. Through various
message passing protocols, processes may communicate directly with one another,
typically      in    a master/slave relationship.    Alternatively,     a "database-centric"
architecture can enable distributed computing to be done without any form of direct inter-
process communication, by utilizing a shared database.




Distributed Computing Paradigms:-


      The Message Passing Paradigm:-

            Message passing is the most fundamental paradigm for distributed applications.
A process sends a message representing a request. The message is delivered to a receiver,
which processes the request, and sends a message in response. In turn, the reply may
trigger a further request, which leads to a subsequent reply, and so forth.




                                             16
   The Client-Server Paradigm:-

             Perhaps the best known paradigm for network applications, the client-server
model assigns asymmetric roles to two collaborating processes. One process, the server,
plays the role of a service provider which waits passively for the arrival of requests. The
other, the client, issues specific requests to the server and awaits its response. Simple in
concept, the client-server model provides an efficient abstraction for the delivery of
network services. Operations required include those for a server process to listen and to
accept requests, and for a client process to issue requests and accept responses. By
assigning asymmetric roles to the two sides, event synchronization is simplified: the
server process waits for requests, and the client in turn waits for responses. Many Internet
services are client-server applications. These services are often known by the protocol
that the application implements. Well known Internet services include HTTP, FTP, DNS,
etc.




                                            16
   The Peer-to-Peer Distributed Computing Paradigm:-

          In the peer-to-peer paradigm, the participating processes play equal roles, with
equivalent capabilities and responsibilities (hence the term “peer”). Each participant may
issue a request to another participant and receive a response. The peer-to-peer paradigm
is more appropriate for applications such as instant messaging, peer-to-peer file transfers,
video conferencing, and collaborative work. It is also possible for an application to be
based on both the client-server model and the peer-to-peer model. A well-known example
of a peer-to-peer file transfer service is Napster.com or similar sites which allow files
(primarily audio files) to be transmitted among computers on the Internet. It makes use of
a server for directory in addition to the peer-to-peer computing.




                                            16
Application:-
     There are many examples of commercial application of distributed system, such as
the Database Management System, distributed computing using mobile agents, local
intranet, internet (World Wide Web), JAVA RMI, etc.


      Distributed Computing Using Mobile Agents:-
           Mobile agents can be wandering around in a network using free resources for
their own computations.




      Local Intranet:-
         A portion of Internet that is separately administered & supports internal sharing
       of resources (file/storage systems and printers) is called local intranet.




                                             16
   Internet:-
     The Internet is a global system of interconnected computer networks that use the
    standardized Internet Protocol Suite (TCP/IP).




                                       16
16
   JAVA RMI:-
 Communicating Entities:-
 Implementing some application for user
 Using support of distributed services
 Layers of support
 Client/server
 Embedded in language Java:-
 Object variant of remote procedure call
 Adds naming compared with RPC
 Restricted to Java environments




                                     16
 RMI Features:-
 Distributed object model:-
 Objects: normal and remote
 Idea:-
 Remote object exists on other host
 Remote object can be used as normal object
 Behavior described by interface
 Environment takes care of remote invocation
 Differences normal and remote objects:-
 Remote references can be distributed freely
 Clients only know/use interface, not actual implementation
 Passing remote objects by reference, normal objects by copying
 Failure handling more complicated since invocation itself can also fail


   RMI Architecture:-




                                       16
Advantages:-
     Economics:-
        Computers harnessed together give a better price/performance ratio than
      mainframes.


     Speed:-
       A distributed system may have more total computing power than a mainframe.


     Inherent distribution of applications:-
       Some applications are inherently distributed. E.g., an ATM-banking application.


                                         16
   Reliability:-
            If one machine crashes, the system as a whole can still survive if you have
multiple server machines and multiple storage devices (redundancy).


      Extensibility and Incremental Growth:-
          Possible to gradually scale up (in terms of processing power and functionality)
   by adding more sources (both hardware and software). This can be done without
   disruption to the rest of the system.



      Distributed custodianship:-
          The National Spatial Data Infrastructure (NSDI) calls for a system of
       partnerships to produce a future national framework for data as a patchwork quilt
       of information collected at different scales and produced and maintained by
       different governments and agencies. NSDI will require novel arrangements for
       framework management, area integration, and data distribution. This research will
       examine the basic feasibility and likely effects of such distributed custodianship
       in the context of distributed computing architectures, and will determine the
       institutional structures that must evolve to support such custodianship.


      Data integration:-
         This research will contribute to the integration of geographic information and
       GISs into the mainstream of future libraries, which are likely to have full digital
       capacity. The digital libraries of the future will offer services for manipulating
       and processing data as well as for simple searches and retrieval.


      Missed opportunities:-



                                            16
By anticipating the impact that a rapidly advancing technology will have on
       GISs, this research will allow the GIS community to take better advantage of the
       opportunities that the technology offers.




Disadvantages:-
    Lack of experience in designing, and implementing a distributed system. E.g.
       which platform (hardware and OS) to use, which language to use etc. But this is
       changing now.
    If the network underlying a distributed system saturates or goes down, then the
       distributed system will be effectively disabled thus negating most of the
       advantages of the distributed system.
    Security is a major hazard since easy access to data means easy access to secret
       data as well.




Conclusions:-
       In this age of optimization everybody is trying to get optimized output from their
limited resources. The concept of distributed computing is the most efficient way to
achieve the optimization. In case of distributed computing the actual task is modularized
and is distributed among various computer system. It not only increases the efficiency of
the task but also reduce the total time required to complete the task. Now the advance
concept of this distributed computing, that is the distributed computing through mobile
agents is setting a new landmark in this technology. A mobile agent is a process that can
transport its state from one environment to another, with its data intact, and be capable of
performing appropriately in the new environment.




                                            16
References:-


   Andrews, Gregory R. (2000), Foundations of Multithreaded, Parallel, and
     Distributed Programming, Addison–Wesley, ISBN 0-201-35752-6.
   Arora, Sanjeev; Barak, Boaz (2009), Computational Complexity – A Modern
     Approach, Cambridge, ISBN 978-0-521-42426-4.
   Cormen,       Thomas       H.; Leiserson,     Charles     E.; Rivest,     Ronald
     L. (1990), Introduction to Algorithms (1st ed.), MIT Press, ISBN 0-262-03141-8.
   Dolev, Shlomi (2000), Self-Stabilization, MIT Press, ISBN 0-262-04178-2.



                                        16
16

More Related Content

What's hot

Distributed Systems
Distributed SystemsDistributed Systems
Distributed SystemsRupsee
 
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
EUDAT
 
Cloud deployment models
Cloud deployment modelsCloud deployment models
Cloud deployment models
Ashok Kumar
 
Application of MapReduce in Cloud Computing
Application of MapReduce in Cloud ComputingApplication of MapReduce in Cloud Computing
Application of MapReduce in Cloud ComputingMohammad Mustaqeem
 
Replication in Distributed Systems
Replication in Distributed SystemsReplication in Distributed Systems
Replication in Distributed Systems
Kavya Barnadhya Hazarika
 
Underlying principles of parallel and distributed computing
Underlying principles of parallel and distributed computingUnderlying principles of parallel and distributed computing
Underlying principles of parallel and distributed computing
GOVERNMENT COLLEGE OF ENGINEERING,TIRUNELVELI
 
Introduction to Virtualization
Introduction to VirtualizationIntroduction to Virtualization
Introduction to Virtualization
Rahul Hada
 
NIST Cloud Computing Reference Architecture
NIST Cloud Computing Reference ArchitectureNIST Cloud Computing Reference Architecture
NIST Cloud Computing Reference Architecture
Thanakrit Lersmethasakul
 
Unit 1 architecture of distributed systems
Unit 1 architecture of distributed systemsUnit 1 architecture of distributed systems
Unit 1 architecture of distributed systemskaran2190
 
System models in distributed system
System models in distributed systemSystem models in distributed system
System models in distributed system
ishapadhy
 
Agreement Protocols, distributed File Systems, Distributed Shared Memory
Agreement Protocols, distributed File Systems, Distributed Shared MemoryAgreement Protocols, distributed File Systems, Distributed Shared Memory
Agreement Protocols, distributed File Systems, Distributed Shared Memory
SHIKHA GAUTAM
 
Cloud computing
Cloud computingCloud computing
Cloud computing
Shiv Ram Choudhury
 
Overview of computing paradigm
Overview of computing paradigmOverview of computing paradigm
Overview of computing paradigm
Ripal Ranpara
 
Process Management-Process Migration
Process Management-Process MigrationProcess Management-Process Migration
Process Management-Process Migration
MNM Jain Engineering College
 
Client Server Architecture
Client Server ArchitectureClient Server Architecture
Client Server Architecture
Ashir Mubeen
 
Distributed Computing ppt
Distributed Computing pptDistributed Computing ppt
Communications is distributed systems
Communications is distributed systemsCommunications is distributed systems
Communications is distributed systems
SHATHAN
 
Data security in cloud computing
Data security in cloud computingData security in cloud computing
Data security in cloud computingPrince Chandu
 
CS8791 Cloud Computing - Question Bank
CS8791 Cloud Computing - Question BankCS8791 Cloud Computing - Question Bank
CS8791 Cloud Computing - Question Bank
pkaviya
 

What's hot (20)

Distributed Systems
Distributed SystemsDistributed Systems
Distributed Systems
 
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
High Performance & High Throughput Computing - EUDAT Summer School (Giuseppe ...
 
Cloud deployment models
Cloud deployment modelsCloud deployment models
Cloud deployment models
 
Application of MapReduce in Cloud Computing
Application of MapReduce in Cloud ComputingApplication of MapReduce in Cloud Computing
Application of MapReduce in Cloud Computing
 
Replication in Distributed Systems
Replication in Distributed SystemsReplication in Distributed Systems
Replication in Distributed Systems
 
Underlying principles of parallel and distributed computing
Underlying principles of parallel and distributed computingUnderlying principles of parallel and distributed computing
Underlying principles of parallel and distributed computing
 
Introduction to Virtualization
Introduction to VirtualizationIntroduction to Virtualization
Introduction to Virtualization
 
NIST Cloud Computing Reference Architecture
NIST Cloud Computing Reference ArchitectureNIST Cloud Computing Reference Architecture
NIST Cloud Computing Reference Architecture
 
Unit 1 architecture of distributed systems
Unit 1 architecture of distributed systemsUnit 1 architecture of distributed systems
Unit 1 architecture of distributed systems
 
System models in distributed system
System models in distributed systemSystem models in distributed system
System models in distributed system
 
Agreement Protocols, distributed File Systems, Distributed Shared Memory
Agreement Protocols, distributed File Systems, Distributed Shared MemoryAgreement Protocols, distributed File Systems, Distributed Shared Memory
Agreement Protocols, distributed File Systems, Distributed Shared Memory
 
Cloud computing
Cloud computingCloud computing
Cloud computing
 
Overview of computing paradigm
Overview of computing paradigmOverview of computing paradigm
Overview of computing paradigm
 
Green cloud
Green cloudGreen cloud
Green cloud
 
Process Management-Process Migration
Process Management-Process MigrationProcess Management-Process Migration
Process Management-Process Migration
 
Client Server Architecture
Client Server ArchitectureClient Server Architecture
Client Server Architecture
 
Distributed Computing ppt
Distributed Computing pptDistributed Computing ppt
Distributed Computing ppt
 
Communications is distributed systems
Communications is distributed systemsCommunications is distributed systems
Communications is distributed systems
 
Data security in cloud computing
Data security in cloud computingData security in cloud computing
Data security in cloud computing
 
CS8791 Cloud Computing - Question Bank
CS8791 Cloud Computing - Question BankCS8791 Cloud Computing - Question Bank
CS8791 Cloud Computing - Question Bank
 

Similar to Distributed Computing Report

paradigms cloud.pptx
paradigms cloud.pptxparadigms cloud.pptx
paradigms cloud.pptx
gunvinit931
 
Distributed architecture (SAD)
Distributed architecture (SAD)Distributed architecture (SAD)
Distributed architecture (SAD)
Khubaib Ahmad Kunjahi
 
Cloud ready reference
Cloud ready referenceCloud ready reference
Cloud ready reference
Helly Patel
 
Distributed computing bsics
Distributed computing bsicsDistributed computing bsics
Distributed computing bsics
Deepak John
 
Distributed Systems.pptx
Distributed Systems.pptxDistributed Systems.pptx
Distributed Systems.pptx
salutiontechnology
 
1.intro. to distributed system
1.intro. to distributed system1.intro. to distributed system
1.intro. to distributed system
Gd Goenka University
 
unit 4-1.pptx
unit 4-1.pptxunit 4-1.pptx
unit 4-1.pptx
prakashvs7
 
DISTRIBUTED SYSTEM 16M.docx
DISTRIBUTED SYSTEM 16M.docxDISTRIBUTED SYSTEM 16M.docx
DISTRIBUTED SYSTEM 16M.docx
20TUCS251VIJAYASHARA
 
D sys ch-vvdp-unit-1
D sys ch-vvdp-unit-1D sys ch-vvdp-unit-1
D sys ch-vvdp-unit-1
shaik subhani
 
Distributed system
Distributed systemDistributed system
Distributed system
chirag patil
 
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT JaipurDistributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
DrNilam Choudhary
 
Distributed system Tanenbaum chapter 1,2,3,4 notes
Distributed system Tanenbaum chapter 1,2,3,4 notes Distributed system Tanenbaum chapter 1,2,3,4 notes
Distributed system Tanenbaum chapter 1,2,3,4 notes
SAhammedShakil
 
Lect 1 Distributed System.pptx
Lect 1 Distributed System.pptxLect 1 Distributed System.pptx
Lect 1 Distributed System.pptx
PardonSamson
 
Computer Networking Theory Assignment 1
Computer Networking Theory Assignment 1Computer Networking Theory Assignment 1
Computer Networking Theory Assignment 1
Hasibul Islam Nirob
 
Chapter 1-Introduction.ppt
Chapter 1-Introduction.pptChapter 1-Introduction.ppt
Chapter 1-Introduction.ppt
balewayalew
 
Chapter One.ppt
Chapter One.pptChapter One.ppt
Chapter One.ppt
abdigeremew
 
OS .pptx
OS .pptxOS .pptx
OS .pptx
alex194654
 
Cloud computing Review over various scheduling algorithms
Cloud computing Review over various scheduling algorithmsCloud computing Review over various scheduling algorithms
Cloud computing Review over various scheduling algorithms
IJEEE
 
Distributed Software Engineering with Client-Server Computing
Distributed Software Engineering with Client-Server ComputingDistributed Software Engineering with Client-Server Computing
Distributed Software Engineering with Client-Server Computing
Haseeb Rehman
 
Computing notes
Computing notesComputing notes
Computing notesthenraju24
 

Similar to Distributed Computing Report (20)

paradigms cloud.pptx
paradigms cloud.pptxparadigms cloud.pptx
paradigms cloud.pptx
 
Distributed architecture (SAD)
Distributed architecture (SAD)Distributed architecture (SAD)
Distributed architecture (SAD)
 
Cloud ready reference
Cloud ready referenceCloud ready reference
Cloud ready reference
 
Distributed computing bsics
Distributed computing bsicsDistributed computing bsics
Distributed computing bsics
 
Distributed Systems.pptx
Distributed Systems.pptxDistributed Systems.pptx
Distributed Systems.pptx
 
1.intro. to distributed system
1.intro. to distributed system1.intro. to distributed system
1.intro. to distributed system
 
unit 4-1.pptx
unit 4-1.pptxunit 4-1.pptx
unit 4-1.pptx
 
DISTRIBUTED SYSTEM 16M.docx
DISTRIBUTED SYSTEM 16M.docxDISTRIBUTED SYSTEM 16M.docx
DISTRIBUTED SYSTEM 16M.docx
 
D sys ch-vvdp-unit-1
D sys ch-vvdp-unit-1D sys ch-vvdp-unit-1
D sys ch-vvdp-unit-1
 
Distributed system
Distributed systemDistributed system
Distributed system
 
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT JaipurDistributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
Distributed System Unit 1 Notes by Dr. Nilam Choudhary, SKIT Jaipur
 
Distributed system Tanenbaum chapter 1,2,3,4 notes
Distributed system Tanenbaum chapter 1,2,3,4 notes Distributed system Tanenbaum chapter 1,2,3,4 notes
Distributed system Tanenbaum chapter 1,2,3,4 notes
 
Lect 1 Distributed System.pptx
Lect 1 Distributed System.pptxLect 1 Distributed System.pptx
Lect 1 Distributed System.pptx
 
Computer Networking Theory Assignment 1
Computer Networking Theory Assignment 1Computer Networking Theory Assignment 1
Computer Networking Theory Assignment 1
 
Chapter 1-Introduction.ppt
Chapter 1-Introduction.pptChapter 1-Introduction.ppt
Chapter 1-Introduction.ppt
 
Chapter One.ppt
Chapter One.pptChapter One.ppt
Chapter One.ppt
 
OS .pptx
OS .pptxOS .pptx
OS .pptx
 
Cloud computing Review over various scheduling algorithms
Cloud computing Review over various scheduling algorithmsCloud computing Review over various scheduling algorithms
Cloud computing Review over various scheduling algorithms
 
Distributed Software Engineering with Client-Server Computing
Distributed Software Engineering with Client-Server ComputingDistributed Software Engineering with Client-Server Computing
Distributed Software Engineering with Client-Server Computing
 
Computing notes
Computing notesComputing notes
Computing notes
 

Recently uploaded

Knowledge engineering: from people to machines and back
Knowledge engineering: from people to machines and backKnowledge engineering: from people to machines and back
Knowledge engineering: from people to machines and back
Elena Simperl
 
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdfFIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance
 
Leading Change strategies and insights for effective change management pdf 1.pdf
Leading Change strategies and insights for effective change management pdf 1.pdfLeading Change strategies and insights for effective change management pdf 1.pdf
Leading Change strategies and insights for effective change management pdf 1.pdf
OnBoard
 
Search and Society: Reimagining Information Access for Radical Futures
Search and Society: Reimagining Information Access for Radical FuturesSearch and Society: Reimagining Information Access for Radical Futures
Search and Society: Reimagining Information Access for Radical Futures
Bhaskar Mitra
 
"Impact of front-end architecture on development cost", Viktor Turskyi
"Impact of front-end architecture on development cost", Viktor Turskyi"Impact of front-end architecture on development cost", Viktor Turskyi
"Impact of front-end architecture on development cost", Viktor Turskyi
Fwdays
 
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdfFIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
FIDO Alliance
 
Essentials of Automations: Optimizing FME Workflows with Parameters
Essentials of Automations: Optimizing FME Workflows with ParametersEssentials of Automations: Optimizing FME Workflows with Parameters
Essentials of Automations: Optimizing FME Workflows with Parameters
Safe Software
 
When stars align: studies in data quality, knowledge graphs, and machine lear...
When stars align: studies in data quality, knowledge graphs, and machine lear...When stars align: studies in data quality, knowledge graphs, and machine lear...
When stars align: studies in data quality, knowledge graphs, and machine lear...
Elena Simperl
 
Neuro-symbolic is not enough, we need neuro-*semantic*
Neuro-symbolic is not enough, we need neuro-*semantic*Neuro-symbolic is not enough, we need neuro-*semantic*
Neuro-symbolic is not enough, we need neuro-*semantic*
Frank van Harmelen
 
Connector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a buttonConnector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a button
DianaGray10
 
DevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA ConnectDevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA Connect
Kari Kakkonen
 
Key Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdfKey Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdf
Cheryl Hung
 
Epistemic Interaction - tuning interfaces to provide information for AI support
Epistemic Interaction - tuning interfaces to provide information for AI supportEpistemic Interaction - tuning interfaces to provide information for AI support
Epistemic Interaction - tuning interfaces to provide information for AI support
Alan Dix
 
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
To Graph or Not to Graph Knowledge Graph Architectures and LLMsTo Graph or Not to Graph Knowledge Graph Architectures and LLMs
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
Paul Groth
 
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
UiPathCommunity
 
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdfSmart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
91mobiles
 
JMeter webinar - integration with InfluxDB and Grafana
JMeter webinar - integration with InfluxDB and GrafanaJMeter webinar - integration with InfluxDB and Grafana
JMeter webinar - integration with InfluxDB and Grafana
RTTS
 
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdfFIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
FIDO Alliance
 
UiPath Test Automation using UiPath Test Suite series, part 4
UiPath Test Automation using UiPath Test Suite series, part 4UiPath Test Automation using UiPath Test Suite series, part 4
UiPath Test Automation using UiPath Test Suite series, part 4
DianaGray10
 
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
Product School
 

Recently uploaded (20)

Knowledge engineering: from people to machines and back
Knowledge engineering: from people to machines and backKnowledge engineering: from people to machines and back
Knowledge engineering: from people to machines and back
 
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdfFIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
FIDO Alliance Osaka Seminar: FIDO Security Aspects.pdf
 
Leading Change strategies and insights for effective change management pdf 1.pdf
Leading Change strategies and insights for effective change management pdf 1.pdfLeading Change strategies and insights for effective change management pdf 1.pdf
Leading Change strategies and insights for effective change management pdf 1.pdf
 
Search and Society: Reimagining Information Access for Radical Futures
Search and Society: Reimagining Information Access for Radical FuturesSearch and Society: Reimagining Information Access for Radical Futures
Search and Society: Reimagining Information Access for Radical Futures
 
"Impact of front-end architecture on development cost", Viktor Turskyi
"Impact of front-end architecture on development cost", Viktor Turskyi"Impact of front-end architecture on development cost", Viktor Turskyi
"Impact of front-end architecture on development cost", Viktor Turskyi
 
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdfFIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
 
Essentials of Automations: Optimizing FME Workflows with Parameters
Essentials of Automations: Optimizing FME Workflows with ParametersEssentials of Automations: Optimizing FME Workflows with Parameters
Essentials of Automations: Optimizing FME Workflows with Parameters
 
When stars align: studies in data quality, knowledge graphs, and machine lear...
When stars align: studies in data quality, knowledge graphs, and machine lear...When stars align: studies in data quality, knowledge graphs, and machine lear...
When stars align: studies in data quality, knowledge graphs, and machine lear...
 
Neuro-symbolic is not enough, we need neuro-*semantic*
Neuro-symbolic is not enough, we need neuro-*semantic*Neuro-symbolic is not enough, we need neuro-*semantic*
Neuro-symbolic is not enough, we need neuro-*semantic*
 
Connector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a buttonConnector Corner: Automate dynamic content and events by pushing a button
Connector Corner: Automate dynamic content and events by pushing a button
 
DevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA ConnectDevOps and Testing slides at DASA Connect
DevOps and Testing slides at DASA Connect
 
Key Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdfKey Trends Shaping the Future of Infrastructure.pdf
Key Trends Shaping the Future of Infrastructure.pdf
 
Epistemic Interaction - tuning interfaces to provide information for AI support
Epistemic Interaction - tuning interfaces to provide information for AI supportEpistemic Interaction - tuning interfaces to provide information for AI support
Epistemic Interaction - tuning interfaces to provide information for AI support
 
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
To Graph or Not to Graph Knowledge Graph Architectures and LLMsTo Graph or Not to Graph Knowledge Graph Architectures and LLMs
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
 
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...
 
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdfSmart TV Buyer Insights Survey 2024 by 91mobiles.pdf
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
 
JMeter webinar - integration with InfluxDB and Grafana
JMeter webinar - integration with InfluxDB and GrafanaJMeter webinar - integration with InfluxDB and Grafana
JMeter webinar - integration with InfluxDB and Grafana
 
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdfFIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf
 
UiPath Test Automation using UiPath Test Suite series, part 4
UiPath Test Automation using UiPath Test Suite series, part 4UiPath Test Automation using UiPath Test Suite series, part 4
UiPath Test Automation using UiPath Test Suite series, part 4
 
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
From Daily Decisions to Bottom Line: Connecting Product Work to Revenue by VP...
 

Distributed Computing Report

  • 1. INTRODUCTION:- In the term distributed computing, the word distributed means spread out across space. Thus, distributed computing is an activity performed on a spatially distributed system. A distributed system consists of collection of autonomous computers, connected through a network and distributed operating system software, which enables computers to coordinate their activities and to share the resources of the system - hardware, software and data, so that users perceive the system as a single, integrated computing facility. 16
  • 2. (Figure 1-Distributed Computing) These networked computers may be in the same room, same campus, same country, or in different continents. A distributed system may have a common goal, such as solving a large computational problem. Alternatively, each computer may have its own 16
  • 3. user with individual needs, and the purpose of the distributed system is to coordinate the use of shared resources or provide communication services to the users. Rise of Distributed Computing:-  Computer hardware prices are falling and power increasing.  Network connectivity is increasing.  Everyone is connected with fat pipes.  It is easy to connect hardware together.  Combination of cheap processors often more  Cost-effective than one expensive fast system.  Flexibility to add according to needs.  Potential increase of reliability.  Sharing of resources. Characteristics of Distributed Computing:- Six key characteristics are primarily responsible for the usefulness of distributed system. They are resource sharing, openness, concurrency, scalability, fault tolerance and transparency. It should be emphasized that they are not automatic consequences of distribution; system must be carefully designed in order to ensure that they are achieved.  Resource Sharing:- Resource sharing is the ability to use any hardware, software or data anywhere in the system. Resources in a distributed system, unlike the centralized one, are physically encapsulated within one of the computers and can only be accessed from others by communication. It is the resource manager to offers a communication interface enabling the resource be accessed, manipulated and updated reliability and consistently. There are mainly two kinds of model resource managers: client/server model and the object-based model. Object Management Group uses the latter one in CORBA, in which any resource 16
  • 4. is treated as an object that encapsulates the resource by means of operations that users can invoke.  Openness:- Openness is concerned with extensions and improvements of distributed systems. New components have to be integrated with existing components so that the added functionality becomes accessible from the distributed system as a whole. Hence, the static and dynamic properties of services provided by components have to be published in detailed interfaces.  Concurrency:- Concurrency arises naturally in distributed systems from the separate activities of users, the independence of resources and the location of server processes in separate computers. Components in distributed systems are executed in concurrent processes. These processes may access the same resource concurrently. Thus the server process must coordinate their actions to ensure system integrity and data integrity.  Scalability:- Scalability concerns the ease of the increasing the scale of the system (e.g. the number of processor) so as to accommodate more users and/or to improve the corresponding responsiveness of the system. Ideally, components should not need to be changed when the scale of a system increases.  Fault tolerance:- Fault tolerance cares the reliability of the system so that in case of failure of hardware, software or network, the system continues to operate properly, without significantly degrading the performance of the system. It may be achieved by recovery (software) and redundancy (both software and hardware). 16
  • 5. Transparency:- Transparency hides the complexity of the distributed systems to the users and application programmers. They can perceive it as a whole rather than a collection of cooperating components in order to reduce the difficulties in design and in operation. This characteristic is orthogonal to the others. There are many aspects of transparency, including access transparency, location transparency, concurrency transparency, replication transparency, failure transparency, migration transparency, performance transparency and scaling transparency. Distributed Computing Architecture:- Various hardware and software architectures are used for distributed computing. At a lower level, it is necessary to interconnect multiple CPUs with some sort of network, regardless of whether that network is printed onto a circuit board or made up of loosely- coupled devices and cables. At a higher level, it is necessary to interconnect processes running on those CPUs with some sort of communication system. Distributed programming typically falls into one of several basic architectures or categories: Client-server, 3-tier architecture, N-tier architecture, Distributed objects, loose coupling, or tight coupling.  Client-server:- Smart client code contacts the server for data, then formats and displays it to the user. Input at the client is committed back to the server when it represents a permanent change. 16
  • 6. 3-tier architecture :- Three tier systems move the client intelligence to a middle tier so that stateless clients can be used. This simplifies application deployment. Most web applications are 3-Tier.  N-tier architecture:- N-Tier refers typically to web applications which further forward their requests to other enterprise services. This type of application is the one most responsible for the success of application servers.  Tightly coupled (clustered):- Tightly coupled architecture refers typically to a cluster of machines that closely work together, running a shared process in parallel. The task is subdivided in parts that are made individually by each one and then put back together to make the final result.  Peer-to-peer:- Peer-to-peer is an architecture where there is no special machine or machines that provide a service or manage the network resources. Instead all responsibilities are uniformly divided among all machines, known as peers. Peers can serve both as clients and servers.  Space based :- Space based refers to an infrastructure that creates the illusion (virtualization) of one single address-space. Data are transparently replicated according to application needs. Decoupling in time, space and reference is achieved. 16
  • 7. Another basic aspect of distributed computing architecture is the method of communicating and coordinating work among concurrent processes. Through various message passing protocols, processes may communicate directly with one another, typically in a master/slave relationship. Alternatively, a "database-centric" architecture can enable distributed computing to be done without any form of direct inter- process communication, by utilizing a shared database. Distributed Computing Paradigms:-  The Message Passing Paradigm:- Message passing is the most fundamental paradigm for distributed applications. A process sends a message representing a request. The message is delivered to a receiver, which processes the request, and sends a message in response. In turn, the reply may trigger a further request, which leads to a subsequent reply, and so forth. 16
  • 8. The Client-Server Paradigm:- Perhaps the best known paradigm for network applications, the client-server model assigns asymmetric roles to two collaborating processes. One process, the server, plays the role of a service provider which waits passively for the arrival of requests. The other, the client, issues specific requests to the server and awaits its response. Simple in concept, the client-server model provides an efficient abstraction for the delivery of network services. Operations required include those for a server process to listen and to accept requests, and for a client process to issue requests and accept responses. By assigning asymmetric roles to the two sides, event synchronization is simplified: the server process waits for requests, and the client in turn waits for responses. Many Internet services are client-server applications. These services are often known by the protocol that the application implements. Well known Internet services include HTTP, FTP, DNS, etc. 16
  • 9. The Peer-to-Peer Distributed Computing Paradigm:- In the peer-to-peer paradigm, the participating processes play equal roles, with equivalent capabilities and responsibilities (hence the term “peer”). Each participant may issue a request to another participant and receive a response. The peer-to-peer paradigm is more appropriate for applications such as instant messaging, peer-to-peer file transfers, video conferencing, and collaborative work. It is also possible for an application to be based on both the client-server model and the peer-to-peer model. A well-known example of a peer-to-peer file transfer service is Napster.com or similar sites which allow files (primarily audio files) to be transmitted among computers on the Internet. It makes use of a server for directory in addition to the peer-to-peer computing. 16
  • 10. Application:- There are many examples of commercial application of distributed system, such as the Database Management System, distributed computing using mobile agents, local intranet, internet (World Wide Web), JAVA RMI, etc.  Distributed Computing Using Mobile Agents:- Mobile agents can be wandering around in a network using free resources for their own computations.  Local Intranet:- A portion of Internet that is separately administered & supports internal sharing of resources (file/storage systems and printers) is called local intranet. 16
  • 11. Internet:- The Internet is a global system of interconnected computer networks that use the standardized Internet Protocol Suite (TCP/IP). 16
  • 12. 16
  • 13. JAVA RMI:-  Communicating Entities:-  Implementing some application for user  Using support of distributed services  Layers of support  Client/server  Embedded in language Java:-  Object variant of remote procedure call  Adds naming compared with RPC  Restricted to Java environments 16
  • 14.  RMI Features:-  Distributed object model:-  Objects: normal and remote  Idea:-  Remote object exists on other host  Remote object can be used as normal object  Behavior described by interface  Environment takes care of remote invocation  Differences normal and remote objects:-  Remote references can be distributed freely  Clients only know/use interface, not actual implementation  Passing remote objects by reference, normal objects by copying  Failure handling more complicated since invocation itself can also fail  RMI Architecture:- 16
  • 15. Advantages:-  Economics:- Computers harnessed together give a better price/performance ratio than mainframes.  Speed:- A distributed system may have more total computing power than a mainframe.  Inherent distribution of applications:- Some applications are inherently distributed. E.g., an ATM-banking application. 16
  • 16. Reliability:- If one machine crashes, the system as a whole can still survive if you have multiple server machines and multiple storage devices (redundancy).  Extensibility and Incremental Growth:- Possible to gradually scale up (in terms of processing power and functionality) by adding more sources (both hardware and software). This can be done without disruption to the rest of the system.  Distributed custodianship:- The National Spatial Data Infrastructure (NSDI) calls for a system of partnerships to produce a future national framework for data as a patchwork quilt of information collected at different scales and produced and maintained by different governments and agencies. NSDI will require novel arrangements for framework management, area integration, and data distribution. This research will examine the basic feasibility and likely effects of such distributed custodianship in the context of distributed computing architectures, and will determine the institutional structures that must evolve to support such custodianship.  Data integration:- This research will contribute to the integration of geographic information and GISs into the mainstream of future libraries, which are likely to have full digital capacity. The digital libraries of the future will offer services for manipulating and processing data as well as for simple searches and retrieval.  Missed opportunities:- 16
  • 17. By anticipating the impact that a rapidly advancing technology will have on GISs, this research will allow the GIS community to take better advantage of the opportunities that the technology offers. Disadvantages:-  Lack of experience in designing, and implementing a distributed system. E.g. which platform (hardware and OS) to use, which language to use etc. But this is changing now.  If the network underlying a distributed system saturates or goes down, then the distributed system will be effectively disabled thus negating most of the advantages of the distributed system.  Security is a major hazard since easy access to data means easy access to secret data as well. Conclusions:- In this age of optimization everybody is trying to get optimized output from their limited resources. The concept of distributed computing is the most efficient way to achieve the optimization. In case of distributed computing the actual task is modularized and is distributed among various computer system. It not only increases the efficiency of the task but also reduce the total time required to complete the task. Now the advance concept of this distributed computing, that is the distributed computing through mobile agents is setting a new landmark in this technology. A mobile agent is a process that can transport its state from one environment to another, with its data intact, and be capable of performing appropriately in the new environment. 16
  • 18. References:-  Andrews, Gregory R. (2000), Foundations of Multithreaded, Parallel, and Distributed Programming, Addison–Wesley, ISBN 0-201-35752-6.  Arora, Sanjeev; Barak, Boaz (2009), Computational Complexity – A Modern Approach, Cambridge, ISBN 978-0-521-42426-4.  Cormen, Thomas H.; Leiserson, Charles E.; Rivest, Ronald L. (1990), Introduction to Algorithms (1st ed.), MIT Press, ISBN 0-262-03141-8.  Dolev, Shlomi (2000), Self-Stabilization, MIT Press, ISBN 0-262-04178-2. 16
  • 19. 16