article 2026-10-30 16 min 2779 views

Designing idempotent POST endpoints without a message bus

A practical walkthrough of architecture with numbers and failure modes.

apiarchitecture

Setup

You need a reproducible load profile before arguing about frameworks. Same payload, same concurrency, same machine.

Method

  1. Warm the process for 30 seconds.
  2. Run fixed concurrency (not “as fast as possible”).
  3. Record p50/p95/p99 and error rate separately.
# example shape — replace with your harness
hey -n 20000 -c 64 https://fast-api.online/api/v1/status

Results shape

Metric Low concurrency High concurrency
RPS stable collapses when pools exhaust
p99 dominated by GC/IO dominated by queueing

Takeaways for Designing idempotent POST endpoints without a message bus

  • Fix the bottleneck you measured, not the blog post you liked.
  • Pool size and worker count interact; change one variable at a time.
  • Publish the command line with the chart or the chart is decoration.

Related