Letting Concurrency Help You Today
summary
Ruby's building blocks get examined with concrete claims and examples: Celluloid actor model powering message-passing concurrency, Sidekiq multi-threaded workers and in-memory Sucker Punch, and Puma's thread pool plus acceptor design with mutex bottlenecks. The difference between concurrency and parallelism is clarified, supervisors and 300,000 to a million actors on BEAM are named as scaling wins, and the claim is that using these abstractions yields clearer design, better latency tails, and practical IO-bound performance today.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:23Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once.
- 7:29programmers love two things: making generalisations, and dismissing other people's generalisations because there are outliers and exceptions
- 10:58management is hard
- 11:09Garbage Collectors
- 11:39Query Generators
- 19:04Multi-threaded
- 22:16Concurrency as a paradigm
- 26:08Web Worker
- 28:19Repo Oriented
- 29:131. Reliability of network
- 29:57Scale independently
- 30:49DEFENDING RUBY
- 31:56Step Two Static or dynamic?
- 33:45ABSTRACTIONS
related talks
39mConcurrent Systems in Ruby
36mModern Concurrency Practices in Ruby
27mIn-Depth Ruby Concurrency: Navigating the Ruby concurrency landscape
36mIntroduction to Concurrency in Ruby
30mAdvanced Multithreading in Ruby
38mModeling concurrency in Ruby and beyond
54mConcurrency: Rubies, plural
35mConcurrency in Ruby: Threads, Fibers and Ractors Demystified