I'm building a round-robin scheduling flow, what should I use?

For a round-robin scheduling flow, the best tool depends on whether you want it to be:

1. Simple and reliable

Use a queue / rotating list pattern.

• Keep agents/users/resources in an ordered list.
• Each assignment takes the next item.
• After assignment, move that item to the end of the list.
• Good for: support tickets, task assignment, lead distribution.

Best if you’re implementing this in code:

• A circular queue
• Or a deque (double-ended queue)

---

2. More scalable / production-ready

Use a persistent state store with atomic updates.

• Store the current pointer/index in a database or cache.
• On each assignment, update it atomically so two requests don’t assign the same person.
• Good for: distributed systems, multiple workers, high concurrency.

Common choices:

• Redis (great for atomic increment/locking)
• PostgreSQL with transactions
• DynamoDB with conditional writes

---

3. Workflow automation / no-code

Use a stateful workflow engine or automation platform.

• If you need routing rules, retries, SLAs, and visibility:
  • Temporal
  • Camunda
  • AWS Step Functions
• If it’s just basic routing:
  • Zapier / Make / n8n

---

Recommended approach

If you’re just starting:

• In-memory: deque / circular queue
• Production with multiple instances: Redis + atomic counter or lock
• Complex business workflow: workflow engine

If you want, I can show you:

1. a simple round-robin algorithm,
2. a Redis-based implementation, or
3. a database schema for round-robin assignment.