SaaSHub helps you find the best software and product alternatives Learn more →
Concurrent Ruby Alternatives
Similar projects and alternatives to Concurrent Ruby
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
-
gems
Ruby Digital Identity & Metaverse Week 2022, September 5th to September 11st - 7 Days of Ruby (Profile Picture & Avatar Character Generation) Gems ++ Best of Ruby Gems Series
-
-
-
-
-
RESTClient
Simple HTTP and REST client for Ruby, inspired by microframework syntax for specifying actions.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Concurrent Ruby discussion
Concurrent Ruby reviews and mentions
- Ruby, Rails, Multi-threading e Puma: Como tudo isso se conecta?
-
Concurrent-ruby (async) S3 files download
Let’s say we need to traverse through thousands of files in our S3 Storage in a Ruby app. Let’s say we have a bunch of logs there that we need to read every day and process. If we just use a straightforward approach, like opening, reading, and processing every file one by one, our solution will work, but It will take a lot of time to process. So we need to improve the speed. Here ruby-concurrent gem is our helper https://github.com/ruby-concurrency/concurrent-ruby. Why do we need this gem? Because It’s simpler to use than Threads and this gem has a lot more features in It. In this article, we will use Concurrent::Promises.future as the most common use of concurrent code. Because reading a file from S3 is an IO operation, we can get a huge benefit in speed if we gonna use concurrent code doing HTTP requests. Remember that concurrency will not give you speed improvements if in every Promise or Thread you will do any calculations. Because of Ruby GIL, every thread will be blocked until calculations are finished.
-
Ruby class pattern to work with API requests with built-in async approach
concurrent-ruby - to add async requests ability. https://github.com/ruby-concurrency/concurrent-ruby
- A Tour of Go Examples in Ruby
-
Exploring concurrent rate limiters, mutexes, semaphores
After this, I took a look at the semaphore class in the popular library, concurrent-ruby to see how they implement it, and I learnt about something new: condition variables. And Ruby comes with this included!
-
My Adventure with Async Ruby
https://github.com/ruby-concurrency/concurrent-ruby has great docs if someone is looking for alternatives.
-
My Adventure With Async Ruby
I wonder how this would compare to using concurrent-ruby under ruby 2.7, especially in a real-world setting (where the calls are actually to external services that return and buffer data, instead of just sleep). The author says that he's felt that ruby threads "feel easy to mess up," but I've found that concurrent-ruby makes it pretty simple, and performant enough even with the GIL.
-
Using Concurrent::Promise while rescuing exceptions in Ruby
As I could not find a clear example about how to rescue exceptions from Concurrent::Promises (part of the Concurrent Ruby gem ) I read through the documentation and here are two examples: one that documents success case and one that shows what is happening when there is an error.
-
Ask HN: Any efforts to remove the GIL for Ruby?
In a sense the GIL (or actually GVL as it's called in current ruby versions) has already been removed for ruby.
It's only the original MRI Ruby that still has it several over Ruby implementations already removed it. e.g. JRuby.
Concurrent-Ruby[1] is probably a good place to start if you want to work with GVL free ruby on JRuby. It's quite well supported and is currently used by Rails.
If you just want async or non-blocking IO I'd take a look at the Async Gem[2]. It looks pretty solid in Ruby > 3.0 and it's been invited by Matz to be part of the stdlib, which I think is a pretty good endorsement.
For MRI itself I don't think it's likely they'll ever remove the GVL. Ractors are probably a better solution for CPU concurrency in the long run, although I think they're pretty experimental currently.
1. https://github.com/ruby-concurrency/concurrent-ruby
-
Intro to Thread-safety in Ruby on Rails
I like how the article exposes you to tools to prove/disprove the problem. I would have hoped it introduced to tools like concurrent ruby and the use of atomics like u/Freeky already mentioned though.
-
A note from our sponsor - SaaSHub
www.saashub.com | 18 May 2025
Stats
ruby-concurrency/concurrent-ruby is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of Concurrent Ruby is Ruby.