Ghasi SMS Gateway
Specs complete · pre-build
Lightweight SMS messaging gateway. Bounded-context companion to the Ghasi suite — one job, done well, integrable from anywhere in the platform.
- Period
- 2025 — present
- Domain
- Communications Infrastructure
- Stack
- API Gateway · IAM
- Per-surface BFFs
- Compliance Engine
- Event Bus
- Provider adapters
- DDD · Outbox
Most platforms accumulate three or four bespoke SMS integrations — one for OTPs, one for marketing, one for transactional alerts. Each carries its own retry semantics, rate-limit handling, and provider failover.
The Gateway consolidates them: a single send port, multiple provider adapters behind it, queue-backed retries, and idempotency keys at the edge.
The layers, ports, and integration patterns are real — drawn from the live architecture baseline. Service names, identity providers, and external vendors are anonymized or labelled by role so the diagram reads as the posture, not as a deployment manifest. Hover any layer label on the left for context; right-edge annotations call out the load-bearing decisions.
— 01 —
Provider adapters behind a single SendPort.
CostAn adapter to write per provider.
WinSwitching providers is a config change, not a code change.
— 02 —
Idempotency keys mandatory at the edge.
CostClients must send a key.
WinRetries are safe; double-sends are structurally impossible.
- Specs: 60 epics, 156 features, 193 user stories.
- Designed to drop into any of the Ghasi platforms as a shared utility service.
- Implementation phase pending.
Founder, lead architect, spec author.
Implementation phase pending; will publish a fuller case study post-V1.