Message queues
At-least-once vs. exactly-once vs. at-most-once paired with business idempotency keys; DLQs, retry backoff, and consumer concurrency.
Category · Distributed systems & architecture
Distributed systems & architecture
5 skills Category 13 of 20
This category tackles system coupling and resilience: queue delivery semantics and idempotency, event-driven contracts and ordering, microservice boundaries via bounded contexts, monorepo task graphs and caching, and backup/RPO/RTO. Together with data and troubleshooting & ADRs it supports long-horizon evolution.
In the hub it is the Architecture theme band. The five entries match the main hub.
Quick links
In depth
Event-driven design
Versioned event schemas, ordering and causality, Saga/TCC trade-offs—avoid event spaghetti.
Microservice boundaries
DDD bounded contexts for ownership and data sovereignty; anti-corruption layers and Conway-aligned team topology.
Monorepo tooling
Nx/Turborepo/Bazel task graphs, remote cache, affected detection—unify lint/test and release orchestration.
Database backup
Full/incremental, off-site replicas, restore drills with measured RTO—ties to disaster recovery playbooks.