Distributed Systems - Chapter 1: Introduction to Distributed Computing

0.0(0)
Studied by 0 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/33

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards covering basic definitions, properties, software architectural styles, NoSQL databases (Cassandra, MongoDB), and streaming platforms (Kafka) from Chapter 1 of Distributed Systems.

Last updated 8:39 AM on 9/7/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

34 Terms

1
New cards

Distributed Computing

The branch of computer science that studies distributed systems and the art of solving complex problems by using multiple computing devices when a single computer is no longer sufficient.

2
New cards

Distributed System

A collection of autonomous components located on different networked nodes (machines) that communicate and coordinate actions strictly via message passing to appear as a single unified system to the end user.

3
New cards
<p>Distributed System Layer (Middleware)</p>

Distributed System Layer (Middleware)

A software layer positioned between distributed applications and local operating systems that enables components on heterogeneous machines to communicate and interact across a network.

4
New cards

Absence of Global Clock

A key characteristic of distributed systems where each node operates on its own local clock at differing rates, resulting in asynchronous operations without a single central time source.

5
New cards

Node Dynamism

The property of a distributed system allowing independent nodes to dynamically join or leave the computing group (open groups), often organized over an overlay network.

6
New cards

Absence of Shared Memory

A characteristic where each computing device in a distributed system possesses its own independent physical memory, preventing any single node from directly knowing the complete global state.

7
New cards

Resource Sharing

The ability of multiple computing devices in a distributed network to share hardware, software components, and data to reduce costs and facilitate seamless information exchange.

8
New cards

Heterogeneity

The variation in networks, hardware, operating systems, programming languages, and software components built by different developers within the same distributed system.

9
New cards

Interoperability

The ability of different hardware and software systems to effectively exchange information through standardized protocols and shared conventions.

10
New cards

Portability

The capability of software components to operate correctly across different operating system environments without requiring core modifications.

11
New cards

Extensibility

The design feature allowing developers to add new capabilities or reimplement existing features in a system without compromising current functionalities.

12
New cards

Scalability

The ability of a system to accommodate growth in service workload, geographic extent, or administrative domain without significant degradation in performance.

13
New cards

Dynamic Reconfiguration

The dynamic binding and adjustment of remote communication interfaces, enabling runtime module substitution, topological alterations, or module migration.

14
New cards

Client-Server Architecture

An architectural model where an application is split into client components that request services and server components that execute and deliver requested services.

15
New cards

Multi-Node Client-Server Architecture

A generalized client-server model where server workloads (processing, scheduling, load balancing) are distributed across multiple machines to execute tasks in parallel.

16
New cards

Service-Oriented Architecture (SOA)

An architectural approach offering service registry, discovery, and binding mechanisms over high-speed networks, often utilizing a pay-per-use model.

17
New cards

Peer-to-Peer (P2P) Architecture

A fully decentralized architecture where every node acts simultaneously as both client and server, sharing computing resources and decision-making directly without central server control.

18
New cards

Microservices Architecture

An architectural style where loosely coupled services encapsulate feature-level business logic and manage independent databases while communicating over a network.

19
New cards

Apache Cassandra

An open-source, column-oriented NoSQL distributed key-value database system created by Facebook in 2008 for handling big data across multiple nodes with high availability and no single point of failure.

20
New cards
<p>Apache Cassandra Cluster Architecture</p>

Apache Cassandra Cluster Architecture

A decentralized ring network structure where 1 installation equals 1 node, offering +1TB capacity and up to 3000 Tx/sec/core throughput, communicating across nodes via gossiping.

21
New cards

Gossip Protocol

A peer-to-peer communication process used by nodes in Apache Cassandra to periodically exchange cluster state information across the network ring.

22
New cards

MongoDB

An open-source, cross-platform, document-oriented NoSQL database developed by MongoDB Inc. (2009) that stores structured data as key-value pairs inside schema-less documents.

23
New cards
<p>MongoDB Features</p>

MongoDB Features

Core features of MongoDB including indexing, schema-less document-oriented storage, replication, auto-sharding, GridFS, aggregation pipelines, ad-hoc queries, and high performance.

24
New cards

BSON

Binary JSON format used internally by MongoDB to encode type and length details for faster binary storage and traversal compared to standard JSON.

25
New cards

_id Index

A unique primary key index built automatically on a B-Tree structure in MongoDB to identify each document uniquely and optimize retrieval operations.

26
New cards

Auto-sharding

A feature in MongoDB that automatically partitions and distributes data across multiple physical server segments (shards) to achieve automated load balancing.

27
New cards

Apache Kafka

An open-source distributed event streaming platform created at LinkedIn in 2011, designed for real-time data pipelines, stream processing, and high-throughput publish-subscribe messaging.

28
New cards
<p>Apache Kafka Architecture</p>

Apache Kafka Architecture

An event streaming ecosystem where producers push records to brokers in a Kafka cluster, consumers pull records from topics, and ZooKeeper coordinates cluster nodes.

29
New cards

Kafka Topic

A logical category or stream name in Apache Kafka where incoming records and messages sent by producers are organized and stored.

30
New cards

Kafka Broker

A server within an Apache Kafka cluster responsible for receiving messages from producers, storing them on disk, and serving them to consumers.

31
New cards

Kafka Producer

An application or data source that generates data streams and publishes messages into one or more specified topics within a Kafka cluster.

32
New cards

Kafka Consumer

An application or data sink that pulls and reads published messages from Kafka brokers and topics when ready to process them.

33
New cards

Kafka Partition

An ordered, immutable sequence of message logs stored within a topic, where each log record is assigned a sequential offset ID.

34
New cards

ZooKeeper

A centralized service used by Apache Kafka to maintain broker cluster metadata, coordinate cluster activities, and facilitate leader selection for partitions.