Clojure core.async: coordinating producer and consumer work without manual thread management
Use core.async channels and go blocks to coordinate Clojure work with blocking-style syntax while parking threads, not blocking OS threads.
Loading…
ReadMeFeed / Community knowledge
#concurrency
Real questions. Useful conversations. Find the people who know your stack.
clojureTuning Cloud Run concurrency: the 80-request trade-off
Cloud Run's default concurrency of 80 drives cost and latency. Learn when to tune it and how to test CPU-bound versus I/O-bound workloads.
cloudrunDart Isolates: Minimal Architecture for CPU-Bound Parallel Work
When Dart UI blocks on CPU work, isolates provide memory-isolated parallelism via message passing. This architecture note covers the minimal design, data boundaries, operational checks, failure modes and when to change the approach.
Bounded In-Process Pipelines with Ruby's SizedQueue and Worker Threads
Use Ruby's SizedQueue and a fixed worker pool to cap memory and apply backpressure in producer-consumer pipelines, with explicit error handling and clear boundaries for shared mutable state.
rubyThrottling Resource Contention with Counting Semaphores
Learn how to use counting semaphores to manage resource pools and throttle API concurrency, avoiding the common pitfalls of permit leaks and priority inversion.
Optimizing Cloud Run Concurrency for Latency and Cost
Learn how to configure Cloud Run concurrency to balance cost and performance. This guide covers the relationship between CPU allocation and request limits with practical deployment examples.
ARM64's Weak Memory Model: Why x86 Code Fails on AArch64
ARM64 does not guarantee x86's store-load ordering. Learn how AArch64's weak memory model breaks plain shared-variable code and how to fix it with acquire/release atomics.
aarch64Managing Process State in Elixir with GenServer: Calls vs. Casts
Learn how to manage process state in Elixir using GenServer, including the critical technical differences between synchronous calls and asynchronous casts to avoid timeouts and mailbox overflows.
Using GitHub Actions Concurrency Groups to Cancel Superseded CI Runs
Multiple quick pushes can trigger redundant GitHub Actions workflows. Learn how concurrency groups with cancel-in-progress reduce CI waste, the trade-offs of aggressive cancellation, and how to configure it safely.
githubactions