cloud-backend-patterns

Choose FIFO when message ordering and exactly-once delivery matter, accepting lower throughput limits. Choose Standard for high-throughput workloads that tolerate duplicates, and make consumers idempotent using dedup tables or idempotency keys.

Follow a 5-step SOP: verify the current identity, list attached policies, simulate the action, check explicit denies from boundaries or control policies, then verify resource-based policies. Never skip identity verification or guess the cause.

Identity-based policies attach to users or roles and define what that identity can do. Resource-based policies attach to the resource and define who can access it, which is essential for multi-tenant isolation scenarios.

Yes, the patterns are cloud-agnostic and include Azure mappings such as Service Bus for SQS, Key Vault for Secrets Manager, and Event Grid for EventBridge. It avoids vendor-specific API calls and focuses on transferable design paradigms.

Refresh tokens in localStorage are vulnerable to XSS attacks that can steal them for persistent access. Store them in httpOnly cookies or secure storage, rotate them on each use, and keep access token lifetimes short.

Use Express for high-throughput tasks under five minutes without retry needs, such as streaming processing. Use Standard for long-running business workflows up to a year that require retry logic, visual debugging, and full audit history.