» Tag
system-design
32 postsKafka vs RabbitMQ: You're Asking the Wrong Question
Choosing Kafka vs RabbitMQ isn't about throughput benchmarks. The real question is queue vs log, and whether you need message replay and multiple consumers.
Orchestrated Agents Over One Prompt: Lessons From a Branding Platform
BrandBrahma's team explains why they chose a four-orchestrator agent architecture over a single LLM call, separating verification tasks from generative ones for reliability.
Generating Procurement Approval Workflows from an Org Graph
Instead of static workflow engines, the organization is modeled as a versioned graph; approvals are computed at runtime, preserving full auditability.
CommitBrief — AI code reviews, right in your terminal
A provider-agnostic, local-first CLI that reviews your staged changes, a historic range, or a whole GitHub pull request. Zero telemetry, no server. Free and open source.
commitbrief.comA Config-Driven Control Plane for Human-in-the-Loop Multi-Agent Systems
A config-driven control plane lets one operator supervise many human-in-the-loop AI agents, using pub/sub routing by capability and a three-message protocol.
Retry is not a loop, it's a data structure
Why treating retries as simple loops instead of data structures silently corrupts ordering, causes duplicates, and breaks distributed system histories.
There Is No "Now" in Distributed Systems
Inspired by Einstein's relativity: NTP clock sync is an illusion. Learn how logical clocks, CAP theorem, and TrueTime solve event ordering in distributed systems.
Why AT Protocol Traded Local-First for Federated Scale
How AT Protocol replaced local-first p2p design with a federated PDS network to meet Twitter-scale replication demands.
A Memory-Bounded HTML-to-PDF Architecture for Bursty Workloads
How a solo-built PDF service uses a Postgres-backed queue and streaming Chromium renders to cap memory use regardless of document size.
Why Multi-Model AI Pipelines Lose the Truth at Handoffs
Model handoffs in multi-agent AI systems can silently erase caveats and evidence, turning careful findings into false certainty without errors.
From Single Agent to Orchestration: When Multi-Agent Systems Pay Off
When to move from a single LLM agent to multi-agent orchestration, the production patterns that matter, and a Rust coordinator/worker example.