from The Open University
Alternatively you can skip the navigation by pressing 'Enter'.
- Thursday 12:04, BBC Radio 4, A History of Ideas
- Thursday 16:30, BBC Radio 4, BBC Inside Science - Epochs and climate change
- Thursday 16:30, BBC Radio 4, BBC Inside Science
- Thursday 20:30, BBC Radio 4, The Bottom Line - The price of time
- Thursday 21:00, BBC Radio 4, BBC Inside Science - Epochs and climate change
This unit looks at some of the architectural and programming paradigms used in...
This unit looks at some of the architectural and programming paradigms used in distributed system development. You will learn about synchronous and asynchronous message passing, distributed objects technology and event-based bus architecture, before finally moving on to tuple architecture.
After studying this unit you should be able to:
- describe some of the architectural and programming paradigms used in distributed system development;
- describe message passing and the role of protocols within a message passing paradigm;
- introduce the concept of a distributed object;
- describe how event-based architectures are used within distributed system development;
- introduce one implementation of an event-based architecture;
- outline the concept of tuple-based development;
- introduce the main ideas behind remote procedure call;
- introduce one commercial example of a tuple-based technology.
- Current section: Introduction
- Learning outcomes
- 1 Distributed models
- 2 Message passing
- 3 Distributed objects technology
- 4 Event-based bus architectures
- 5 Tuple architecture
- 6 Further reading
In this unit I look at a number of different programming and design styles associated with distributed system development. The unit first examines message passing and the role of protocols – both fixed and adaptive protocols. Two styles of message passing are also examined: synchronous and asynchronous message passing. The next part of the unit introduces distributed object technology. Event-based development relies on listener objects listening to events which are propagated along a bus; the unit looks at this form of implementation and details its relationship to multicasting. A commercial implementation of event-based technology is presented. The unit also includes a description of the oldest paradigm: remote procedure call. The unit concludes with a description of the most abstract model we have available for distributed system development: that of tuple architectures. A Java implementation known as JavaSpaces concludes the unit.
Adaptive protocol, API, asynchronous message passing, distributed event. distributed object, fixed protocol, hub and spoke architecture, interface definition language, message passing, multicast bus architecture, multicasting, protocol, pull technology, push technology, remote procedure call, RPC-XML, space, synchronous message passing, tuple.
This unit is from our archive and is an adapted extract from Distributed Applications and eCommerce (M879) which is no longer taught by The Open University. If you want to study formally with us, you may wish to explore other courses we offer in.
This is an extract from an Open University course which is no longer available to new students. If you found this interesting you could explore more free Systems (Computer) course units or view the range of currently available OU Systems (Computer) courses.