Concurrent Ruby

Modern concurrency tools including agents, futures, promises, thread pools, supervisors, and more. Inspired by Erlang, Clojure, Scala, Go, Java, JavaScript, and classic concurrency patterns. (by ruby-concurrency)

Concurrent Ruby Alternatives

Similar projects and alternatives to Concurrent Ruby

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Concurrent Ruby alternative or higher similarity.

Concurrent Ruby discussion

Log in or Post with

Concurrent Ruby reviews and mentions

Posts with mentions or reviews of Concurrent Ruby. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-05-16.
  • Concurrent-ruby (async) S3 files download
    1 project | | 17 May 2024
    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 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
    8 projects | | 16 May 2024
    concurrent-ruby - to add async requests ability.
  • A Tour of Go Examples in Ruby
    1 project | | 16 Mar 2024
  • Exploring concurrent rate limiters, mutexes, semaphores
    2 projects | | 11 Sep 2023
    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
    1 project | | 3 Sep 2023 has great docs if someone is looking for alternatives.
  • My Adventure With Async Ruby
    1 project | /r/ruby | 23 Jan 2023
    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
    2 projects | | 12 Aug 2022
    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?
    2 projects | | 15 Jun 2022
    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.


  • Intro to Thread-safety in Ruby on Rails
    1 project | /r/ruby | 23 Mar 2022
    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.
  • How to get results from Concurrent::Promise::all?
    1 project | /r/ruby | 11 Mar 2022
    Using conccurrent-ruby, how can I execute a set of promises and then get the results?
  • A note from our sponsor - SaaSHub | 21 Jun 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic Concurrent Ruby repo stats
12 days ago

Rennaisance engineers rejoice! 1 gem 5 min to app monitoring
5-minute onboarding. No sales team. Devs in the support channels. No DevOps team required. Get the free app insights every engineer deserves with Scout Monitoring.