Auth service
Authenticates callers and issues/validates tokens; enforces authorisation.
Problem it solves: Who is calling, and what may they do?
Where it sits: Called by the gateway or services.
When to use
- Any multi-user system.
Failure modes
- Auth outage blocks all traffic — cache token validation.
Metrics to watch
- Auth latency
- Login failures
Alternatives
- Stateless JWT validation at gateway
Configuration in Labs (illustrative defaults)
- Instances (count) = 2 — Identical copies behind this logical component. Capacity scales linearly in this model.
- Capacity per instance (req/s) = 5000 — Maximum requests one instance completes per second before it saturates.
- Base service time (ms) = 5 — Processing time per request at zero load. Queueing adds to this as utilisation rises.