Study Notes
search
⌘Ctrlk
Study Notes
  • Introduction
  • Architecture & System Design
    • Messaging Systems
    • RPC Frameworks
    • Scalable Web Application Architecture
    • Parallel vs Concurrent
    • Concurrency
    • Load Balancing - Nginx
    • REST API
    • WebSockets
    • Streaming
    • Serialization
  • Programming Language
    • JavaScript & Node.js
    • Java
    • Erlang
    • Python
    • Golang
  • Software Engineering
    • Design Patterns
    • Unit Testing
    • Legacy Code
    • Agile & Scrum
  • Database
    • NoSQL
    • SQL
  • DevOps & Tools
    • Version Control - Git
    • Shell - zsh, bash
    • Docker
    • Linux Package Management - YUM
    • Linux Command Line Tools
  • Security
    • OWASP Security
  • AI, ML, DL, CV, NLP
    • Deep Learning
gitbookPowered by GitBook
block-quoteOn this pagechevron-down
  1. Architecture & System Design

Concurrency

hashtag
Problems

hashtag
Dining philosophers problem

Wikipedia: https://en.wikipedia.org/wiki/Dining_philosophers_problemarrow-up-right

http://adit.io/posts/2013-05-11-The-Dining-Philosophers-Problem-With-Ron-Swanson.htmlarrow-up-right

https://rosettacode.org/wiki/Dining_philosophersarrow-up-right

https://sudocoding.xyz/dining-philosophers-problem-golang/arrow-up-right

https://www.baeldung.com/java-dining-philoshophersarrow-up-right

The problem was designed to illustrate the challenges of avoiding deadlock, a system state in which no progress is possible.

PreviousParallel vs Concurrentchevron-leftNextLoad Balancing - Nginxchevron-right

Last updated 5 years ago

  • Problems
  • Dining philosophers problem