Flexible, Reliable, Distributed Software
1.TeleMed Case
- 1.1Learning Objectives
- 1.2TeleMed Stories
- 1.3A Role Based Design
- 1.4A Server side Role based Design
- 1.5Related Work
2.Basic Concepts
- 2.1The Issues Involved
- 2.2Elements of a Solution
- JSON Libraries
- 2.3Tying Things Together
- 2.4Summary of Key Concepts
- 2.5Review Questions
3.Broker Part One
- 3.1Learning Objectives
- 3.2The Problem
- 3.3The Broker Pattern
- 3.4Analysis
- 3.5Summary of Key Concepts
- 3.6Review Questions
- Architecture Pattern: Broker
4.Implementing Broker
- 4.1Learning Objectives
- 4.2Architectural Concerns
- 4.3Domain Layer
- 4.4Client Side
- 4.5Server side
- 4.6Test-driven development of Distributed Systems
- 4.7Using the Broker library
- 4.8Summary of Key Concepts
5.Broker Part Two
- 5.1Learning Objectives
- 5.2Limitations in the TeleMed Case
- 5.3Game Lobby Stories
- 5.4Walkthrough of a Solution
- 5.5Summary of Key Concepts
- Transferring Server Created Objects
- Transferring Server Objects
- Multi Type Dispatching
- 5.6Review Questions
6.HTTP
- 6.1Learning Objectives
- 6.2A HTTP Walk-through
- Httpie
- 6.3A HTTP Case Study: PasteBin
- 6.4Broker using HTTP
- 6.5Summary of Key Concepts
- 6.6Review Questions
7.REST
- 7.1Learning Objectives
- 7.2The Demise of Broker Architectures
- 7.3Representational State Transfer (REST)
- 7.4Richardson’s model for Levels in REST
- 7.5The Architectural Style
- 7.6Level 1 REST: TeleMed
- 7.7Documenting REST API
- 7.8Continued REST Design for TeleMed
- 7.9Implementing REST based TeleMed
- 7.10Level 2 REST: GameLobby
- 7.11Testability and TDD of REST designs
- 7.12Summary of Key Concepts
- 7.13Review Questions