Async Ruby Alternatives

Async Ruby reviews and mentions

• Rack for Ruby: Socket Hijacking
  1 project | dev.to | 4 Dec 2024

  Since the threading problem is specific to the Puma web server, let's look at another option: Falcon. This is a new, highly concurrent Rack-compliant web server built on the async gem. It uses Ruby Fibers instead of Threads, which are cheaper to create and have much lower overhead.

• Persistent Redis Connections in Sidekiq with Async::Redis: A Deep Dive.
  4 projects | dev.to | 18 Jul 2024

  Async is a composable asynchronous I/O framework for Ruby. It allows you to do things concurrently using Fibers. Since 3.0, Ruby has a fiber scheduler and Ruby core supports it. This means you can have non-blocking I/O without much effort, for example, when using Net::HTTP. If you perform a blocking operation, such as an HTTP call, inside a fiber, it will immediately yield so that another fiber can become active and do some useful work instead of blocking and waiting for the HTTP call to complete.

• EventMachine Performance Spikes
  2 projects | /r/ruby | 5 Sep 2023

  The Async gem is the natural successor, It's actively maintained, and allows you write synchronous code is if it wasn't non-blocking, and most libraries don't need any special support for Async (exceptions are gems with C extensions that do I/O and DB libraries with connection pooling that would otherwise be thread-based).

• Philosophy of Coroutines
  7 projects | news.ycombinator.com | 1 Sep 2023

  https://github.com/socketry/async uses coroutines and I think in general it’s been a great model with very few downsides in practice.

• Is ruby really slow?
  2 projects | /r/ruby | 21 Apr 2023

  There's async I/O. Here's a library that leans on Ruby 3's fiber scheduler.

• Show HN: Goru, an experimental, Go-inspired concurrency library for Ruby
  2 projects | news.ycombinator.com | 3 Apr 2023

  Hey folks, wanted to show this off and get feedback. Still early/experimental but there are quite a few concepts I'm excited about here. This project came about while writing a program in Go and loving its approach to concurrency. Being a long-time Rubyist I immediately started to think about what similar concepts might look like in Ruby.

  I set out with two main design constraints:

  1. Lightweight: I didn't want routines to be backed by fibers or threads. Having been involved some in the async project (https://github.com/socketry/async), I had some experience using fibers for concurrency but was curious if they could be avoided.

  2. Explicitness: Routine behavior must be written to describe exactly how it is to behave. I always felt like concurrent code was hard to fully understand because of the indirection involved. On the spectrum between tedium and magical I wanted to err more on the side of tedium with Goru.

  Goru routines are just blocks that are called once for every tick of the reactor. It is up to the developer to implement behavior in terms of a state machine, where on each tick the routine takes some action and then updates the state of the routine for the next tick. This fulfills both design constraints:

  1. Because routines are just blocks, they weigh in at about ~345 bytes of memory overhead.

  2. Routine behavior is explicit because it is written as a state machine inside the block.

  Couple more features worth noting:

  * Goru includes channels for buffered reading/writing (similar to channels in Go).

  * Goru ships with primitives for non-blocking IO to easily build things like http servers.

  Curious your thoughts!

• Twitter (re)Releases Recommendation Algorithm on GitHub
  12 projects | /r/programming | 31 Mar 2023
• Simple MapReduce that melt my brain (yes, fibers there)
  3 projects | /r/ruby | 16 Mar 2023

  For those who are interested here is the question.

• How does Ruby handle parallel HTTP requests in separate threads?
  3 projects | /r/ruby | 2 Mar 2023
• Two months into learning Ruby, it is the most beautiful language I ever learned
  5 projects | /r/ruby | 25 Feb 2023

  Welcome! Ruby isn't exactly "dying", but the hype/popularity is definitely fading. This is primarily because Ruby is no longer "new", most of Ruby's popularity came from Rails, and now Rails is no longer the "new hotness". However, Ruby still has lots of awesome features and lots of awesome other libraries and frameworks, such as the new fancy irb gem that uses reline, nokogiri, chunky_png, the async gems, Dragon Ruby, SciRuby, Ronin, and the new Hanami web framework.

• A note from our sponsor - SaaSHub
  www.saashub.com | 12 Jan 2025

  SaaSHub helps you find the best software and product alternatives Learn more →