Safest path to concurrency
from JRuby wiki
- Don’t do it.
- If you must do it, don’t share data across threads.
- If you must share data across threads, don’t share mutable data.
- If you must share mutable data across threads, synchronize access to that data.
Do not communicate by sharing data; instead, share data by communicating
Writing Thread-safe Code
Avoid mutating globals
- The AST
- Class variables/methods
Create more objects, rather than sharing one
- Connection pools
Avoid lazy loading
- No autoload
Prefer data structures over mutexes
Mutexes are notoriously hard to use correctly. For better or worse, you have a lot of things to decide when using a mutex.
- How coarse or fine should this mutex be?
- Which lines of code need to be in the critical section?
- Is a deadlock possible here?
- Do I need a per-instance mutex? Or a global one?
By leaning on a data structure, you remove the burden of correct synchronization from your code and depend on the semantics of the data structure to keep things consistent.
Wrap your threads in an abstraction
- Actor model
- Reactor Pattern, event-driven I/O
Into the Wild
Thread-safe Data Structure
- hamster - Efficient, Immutable, Thread-Safe Collection classes for Ruby
- thread_safe - Thread-safe collections for Ruby
- atomic - Atomic references for Ruby (merged with concurrent-ruby)
- connection_pool - Generic connection pooling for Ruby
Abstraction / Framework
Actor-based concurrent object framework for Ruby.
- Reel - An “evented” web server based on Celluloid::IO
- angelo - Sinatra-like DSL for Reel that supports WebSockets and SSE
EventMachine is an event-driven I/O and lightweight concurrency library for Ruby. It provides event-driven I/O using the Reactor pattern.
- Thin, Goliath - Scalable event-driven servers. Examples:
- em-http-request - Asynchronous HTTP Client (EventMachine + Ruby)
- em-synchrony - Fiber aware EventMachine clients and convenience classes
A ruby web server built for concurrency