Notes
FOQS-Style Event Orchestration for Microservices
A practical breakdown of priority queues, retry policy, and dispatch discipline in asynchronous architectures.
Distributed SystemsKafkaMicroservices
The scheduler worked best when urgency and readiness were modeled separately, preventing hot retries from starving critical new work.
Separating durable state from orchestration workers kept scale-out simple while making failures easier to replay and inspect.
A strict retry budget with DLQ routing made failure behavior transparent and significantly improved incident debugging speed.
This section is designed to scale into longer essays later. Add richer Markdown-style content directly in
src/content/portfolio.tsfor each entry.