Skip to content
all episodes
Code of Architecture · episode 21

Distributed Systems — Episode 1

1:20:04

Episode participants

  • Alexander Krasnov

    guest

  • Anton Kosterin

    guest

Conversation

What we discussed on the recording

The first Distributed Systems episode examines what makes a system distributed. Graph topology is not enough: autonomous computing elements, network interaction, and a single-system view all matter. Decentralization can arise from administrative boundaries rather than only from removing a central node.

Membership governs how nodes enter and leave, while an overlay creates a logical network above the physical one. Middleware hides some platform differences but cannot remove partial failures. The authors separate logical design from physical deployment: one logical service may span many machines, zones, and replicas.

Design goals begin with resource sharing and distribution transparency. Open interfaces and dependability follow: availability, reliability, safety, and maintainability are distinct qualities. Maintainability matters for any long-lived system that must evolve after launch.

Scalability is tested across size, geography, and administrative domains. Scale up, scale out, partitioning, asynchronous work, and avoiding global broadcast address different limits. The finale connects these principles to computing, transactional, and pervasive systems.

Book series
Distributed Systems
Maarten van Steen, Andrew S. Tanenbaum
Book playlist