Question 1

How do I test Castor actors without flaky race conditions?

Accepted Answer

Use the Context.Test class to run actors single-threaded and call waitForInactivity() to ensure all messages are processed deterministically, as shown in the debugging examples—this avoids unreliable timing-based assertions.

Question 2

Castor vs Akka: which one should I choose for my Scala project?

Accepted Answer

Castor is better for lightweight, in-process concurrency with simpler setup and type safety, while Akka is suited for distributed systems with fault tolerance. Choose Castor if you don't need clustering and value minimal overhead.

Question 3

Does Castor support batch processing for efficiency?

Accepted Answer

Yes, via BatchActor which allows handling groups of messages in runBatch, useful for batching database queries or API calls to improve performance, as demonstrated in the batch logging example.

Question 4

How to implement a state machine with debounced actions in Castor?

Accepted Answer

Use StateMachineActor to define states like Idle and Buffering, and schedule messages with ac.scheduleMsg for debouncing, as shown in the debounced logging example—this enforces explicit state transitions.

Question 5

Can I use Castor with Scala.js for browser-based applications?

Accepted Answer

Yes, Castor supports Scala.js for single-threaded environments like browsers, allowing concurrent actor patterns in client-side code, as mentioned in the cross-platform feature.

Question 6

What's the error handling strategy in Castor actors?

Accepted Answer

Exceptions thrown during message processing are reported to the Context's reportFailure function (defaults to console printing), and the actor continues processing, so manual error handling is required for robustness.

castor

What is castor?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions