Post #2 of the distributed computing discussion series
Once defined, model will help us understand many features and flavours of distributed computing challenges and put them in perspective and allow us to formulate workarounds or solutions to solve or overcome those challenges. These models will be used throughout in our next set of blogs related to the topic. Hence it is important to focus on the subject and understand clearly.
How do we visualize a distributed system?
Here is how I would describe a distributed system in simple terms.
Previous post gave the high level introduction of the distributed system. In this post we will discuss about model of distributed system.
Once defined, model will help us understand many features and flavours of distributed computing challenges and put them in perspective and allow us to formulate workarounds or solutions to solve or overcome those challenges. These models will be used throughout in our next set of blogs related to the topic. Hence it is important to focus on the subject and understand clearly.
How do we visualize a distributed system?
Here is how I would describe a distributed system in simple terms.
- message passing system - nodes interact by sending/receiving messages
- loosely coupled - no upper bound on message arrival time
- no shared memory - all nodes have their own private memory
- no global clock - clocks of different nodes can't be synchronized globally
- a graph topology - consisting of processes as graph nodes and channels for message passing as edges (directional)
- ordering of messages are not assumed in channels