To Thread or Not to Thread: An In-Depth Look at Ruby’s Execution Models — Development (2022)
shopify.engineering · 3,140 words · saved by 1 readers
An in-depth look at threads vs processes in Ruby web applications, and when you should use each.
blog | Development To Thread or Not to Thread: An In-Depth Look at Ruby’s Execution Models An in-depth look at threads vs processes in Ruby web applications, and when you should use each. Published on May 31, 2022 Deploying Ruby applications using threaded servers has become widely considered as standard practice in recent years. According to the 2022 Ruby on Rails community survey , in which over 2,600 members of the global Rails community responded to a series of questions regarding their experience using Rails, threaded web servers such as Puma are by far the most popular deployment target.
saved by
related reading
- Fixing the Dependency Confusion Vulnerability in 600+ Ruby Apps - Shopifyshopify.engineering
- combinators in Rubymooreniemi.github.io
- Programming language evolution: with all that, we are still flyingzverok.github.io
- Everything I know about good system designseangoedecke.com
- Using Threads to Run Code Simultaneously - The Rust Programming Languagedoc.rust-lang.org
- Concurrency Patterns in Embedded Rust - Ferrous Systemsferrous-systems.com
- Why choose async/await over threads? | Hacker Newsnews.ycombinator.com
- WebSockets, caution required!samsaffron.com
- (Quite) A Few Words About Asyncyoric.github.io
- The Alternative Implementation Problempointersgonewild.com
- Processes and Threads — PlanetScaleplanetscale.com
- Production Twitter on One Machine? 100Gbps NICs and NVMe are fast - Tristan Humethume.ca