システムデザイン周り目次マトリクス

System Design Problems

System Design interviews: A step by step guide

Designing a URL Shortening service like TinyURL

Designing Pastebin

Designing Instagram

Designing Dropbox

Designing Facebook messenger

Designing Twitter

Designing Youtube or Netflix

Designing Typeahead Suggestion

Designing an API Rate Limiter

Designing Twitter Search

Designing a Web Crawler

Designing Facebook's Newsfeed

Designing Yelp or Nearby Friends

Designing Uber backend

Designing Ticketmaster

Additional Resources

Glossary of System Design Basics

System Design Basics

Key Characteristics of Distributed Systems

Load Balancing

Caching

Data Partitioning

Indexes

Proxies

Redundancy and Replication

SQL vs. NoSQL

CAP Theorem

PACELC Theorem

Consistent Hashing

Long-Polling vs WebSockets vs Server-Sent Events

Bloom Filters

Quorum

Leader and Follower

Heartbeat

Checksum

Appendix

Reactive Architecture(1): Introduction to Reactive Systems

Introduction to the Course

Introduction

Course Prerequisites

Why Reactive

Why Reactive (5 Questions)

Case Study: History of the Reactive BBQ (5 Questions)

Discussion: Unresponsive Software

Case Study: The Unresponsive BBQ (6 Questions)

The Goal (6 Questions)

The Reactive Principles

The Reactive Principles (9 Questions)

Case Study: Reactive Principles in Action (4 Questions)

Discussion: Responsive Software

Reactive Systems vs Reactive Programming

Reactive Programming (5 Questions)

The Actor Model (10 Questions)

Final Exam

Exam Instructions

Final Exam (6 Questions)

Patterns of Enterprise Application Architecture