Production
Subscription Activator
Suspension is easy to trigger and expensive to leave in place. The manual remedy was a runbook: someone notices, someone queries, someone restores. That process scales with headcount and fails quietly at night.
The activator turns it into a daemon. It continuously discovers suspended subscriptions, evaluates each against restoration criteria, and acts on the ones that qualify, with Redis for coordination, GraphQL to the platform, and Nomad for scheduling.
Designed, implemented and operated in production.
Go · Redis · GraphQL · Nomad · in production