The Anatomy of a Distributed System

QCon San Francisco International Software Conference is back this November 18-22, 2024. Software leaders at early adopter companies will come together to share actionable insights to help you adopt the right technologies and practices.
Get exposed to new ideas and innovative approaches to software development and engineering, guaranteed to inspire and challenge you.
Don’t miss this opportunity to take your knowledge and skills to the next level and stay ahead in the fast-paced world of technology.
Register now: bit.ly/3Tc73rM
----------------------------------------------------------------------------------------------------------------------------
Read the transcript of the presentation on InfoQ: bit.ly/2F18vTU
Tyler McMullen talks through the components and design of a real system, as well as the theory behind them. The system is built to perform very high volumes of health checks, done across a cluster of machines for reliability and scalability. It includes things like gossip, failure detection, leader election, logical clocks, and consistency trade-offs.
This presentation was recorded at QCon San Francisco 2017.

[@ramamoorthy.n]

A load of information in 30+ minutes, the complex concepts are explained very well.

[@Rarez2]

Distributed Systems concepts:
- Load balancing
- Autoscaling groups
- Determining ownership
- Failure detection
- Communication (ie task/job/event queuing in more modern concepts)
- Convergence (ie statefulness in modern terms)

[@karimmanaouil9354]

This talk is very precious. Thanks.

[@maylodiseyed1687]

Great talk thanks for upload

[@umamahesh8774]

Great Talk & Presentation. Thanks for uploading.

[@vitorleandroloureiro]

Jesus Christ talking about tech stuff, 2018 year is so cool :D

[@quindarius]

Awesome talk homeslice

[@Kaslor1000]

Great talk.

[@sandyz1000]

Entity of Distributed System:
- Load balancing/Ownership: Rendezvous hashing
- Failure detection: Memberlist/SWIM
- Gossip: Communication
- CRDT: Coordination free distributed map - For managing causality

[@stack.1]

Awesome talk

[@vishnukl]

Great talk

[@MsEvgeniyK]

For me it's sounds like an akka cluster description: delta-crdt + gossip

[@cbjueueiwyru7472]

u up?

[@kartavyaramnani1255]

Who's here after Fastly downtime took down the internet ? :P

[@Rarez2]

So basically, "Distributed Systems" is an academic term for architecting highly available, fault tolerant applications & services on AWS/GCP. Rather than using very generic terms, or whole concepts, you would use the specific clouds ervice name: ie Route53, CloudFront, EMR, EKS, Lambda, CloudWatch, AutoScaling Groups, etc etc.

[@pivotal-ai]

Because "simple"