Add ruby-reactor to Ruby libraries section

[arturictus]

A dynamic, dependency-resolving saga orchestrator for Ruby. Ruby Reactor implements the Saga pattern with compensation-based error handling and DAG-based execution planning. It leverages Sidekiq for asynchronous execution and Redis for state persistence.

Project

ruby-reactor: Ruby Reactor implements the Saga pattern with compensation-based error handling and DAG-based execution planning. It supports async execution via Sidekiq and persistence via Redis.

Urls:

• github
• rubygems

What is this Ruby project?

ruby_reactor is a declarative workflow engine and logic orchestrator for Ruby. It provides a structured DSL to define complex business processes as a series of discrete, manageable steps. By encapsulating logic into "Reactors," it helps developers move away from bloated service objects and deeply nested conditional logic toward a more maintainable and observable architecture.

Key Features:

• Step-Based DSL: Define your execution flow using clear step definitions that separate business logic from control flow.
• Resilient Retry Logic: Native support for RetryContext, allowing granular control over how individual steps handle failures and recoveries.
• Contextual Data Flow: Manages a centralized execution context that safely carries data through transformations and validations across the entire workflow.
• Error Handling & Callbacks: Built-in hooks for success, failure, and error states, ensuring that edge cases are handled predictably.
• Developer Productivity: Simplifies testing by allowing developers to test individual steps in isolation rather than testing one massive "god object."

What are the main difference between this Ruby project and similar ones?

ruby_reactor bridges the gap between simple service objects and complex state machine gems by focusing on the execution lifecycle.

• vs. Interactor / Service Objects: While Interactors provide a simple call chain, ruby_reactor offers much more robust error handling and step-level retry mechanisms. It is designed for processes where failure is expected (like 3rd party APIs) and needs to be managed gracefully.
• vs. AASM / State Machines: Traditional state machine gems focus on the state of a database record (the "What"). ruby_reactor focuses on the logic of the process itself (the "How"). It doesn't require a persistent database state to manage complex branching and retries.
• vs. Trailblazer (Operation): ruby_reactor is significantly lighter and easier to integrate into existing Rails or Hanami projects. It provides the "Operation" pattern's benefits—like Railway Oriented Programming—without the steep learning curve or heavy architectural overhead of the full Trailblazer ecosystem.
• vs. Sidekiq/Background Workers: It is the perfect companion to background jobs. Instead of writing a massive, hard-to-debug perform method, you use ruby_reactor to define the logic, making the worker a simple wrapper that triggers the Reactor.

---

Please help us to maintain this collection by using reactions (👍, 👎) and comments to express your feelings.

[markets]

@arturictus still too fresh for this list! As stated in our contrib guides, the projects should be relevant (at least 30k downloads) in the Ruby ecosystem.