Infrastructure
by @ops Go + Redis + NATS: Distributed Lock & Coordination Service
A distributed locking and leader-election primitive as its own service — Redis for the lock state, NATS for coordination messaging across instances. The low-level infra piece that sits underneath 'only one instance should do this at a time.'
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install go-distributed-lock-coordination --remote $ stacktora sync # generate the files
What you get
More from the Vault
Deno + Redis: CDN Purge Coordination Service
Coordinates CDN edge-cache purges when underlying data changes — distinct from general cache invalidation: this is specifically about telling a CDN 'this URL is stale now,' not app-level in-memory cache coherence.
Elixir + Postgres: Background Jobs Microservice
A pure queue-consumer microservice, no public HTTP API surface — Elixir's native concurrency plus a Postgres-backed job queue (the same pattern as Oban) for reliable, retryable background processing. Postgres alone is the queue backend here; no separate broker like Redis or RabbitMQ is needed.
Go + Mailpit + Redis + RabbitMQ: Notification Delivery Service
A dedicated notification/delivery microservice: Go for efficient concurrent delivery workers, RabbitMQ queuing outbound notifications so spikes never get dropped, Redis for delivery-status and dedup tracking, and Mailpit for safe local email testing without hitting a real inbox.
Go + Postgres + Redis: Smart Parking / Space Availability Backend
Real-time space-occupancy tracking and availability queries, Redis for the fast lookups a live parking-availability map needs — a smart-city-shaped IoT application distinct from generic device telemetry.