Orchestrator — Microservice Integration Patterns

Building a distributed Rust backend requires specialized "glue" code to connect web frameworks, background workers, and databases securely. This skill provides the architectural patterns needed to stitch these components together.

Quick Reference: Which Guide Do I Need?

• Fast secret lookups, Argon2id hashing, timing-attack prevention -> Read references/crypto-auth.md
• TOML catalog parsing, Serde, Clap CLI subcommands -> Read references/config-dynamic.md
• Streaming events from Workers to API via Redis Pub/Sub -> Read references/distributed-sse.md
• External RPC SSRF protection for reqwest/Hyper -> Read references/ssrf-protection.md
• ULID task IDs stored as 16-byte SQL values -> Read references/ulid-sqlx.md
• Presigned PUT size limits via S3 bucket policy -> Read references/s3-bucket-policy.md

Core Patterns at a Glance

1. Secure Crypto Auth & Lookups

When dealing with secret identifiers (like a 20-digit Space ID), never store them in plaintext, and never use slow hashes (like Argon2id) for database SELECT lookups. Instead, use a two-step approach: