Originally published on the Tines Engineering Blog.

One of the more fun and challenging problems I worked on at Tines - redesigning how we orchestrate action runs so that no single customer’s workflow can starve everyone else. With over a billion automated actions flowing through the platform every week, our initial simple approach needed an upgrade. We built a fair-share system that pairs deterministic concurrency gating with continuously accruing per-story budgets, and the result is much more predictable performance across the board.

Read the full post on the Tines blog →