Reliable payments, observable recovery.
A portfolio project built around the hardest payment question: did the provider charge the customer when the response timed out?
A timeout is not a decline.
The fake provider stores a successful charge, then withholds its response. PayGuard stores UNKNOWN, its worker later checks the provider, and the same payment becomes SUCCESS. A duplicate client request with the same idempotency key receives the original ID.
From source to operations.
Request and recovery
API, provider, schema, Docker, Kubernetes, Terraform, and Ansible.
02 / LEARNInterview explanations
Why each technology exists, what flows between components, and where to read the code.
03 / MONITORSLIs, SLOs, metrics, logs
Clear definitions, query examples, and links to rules and dashboards.
04 / DASHBOARDWatch recovery happen
Explore the scenario and understand SRE signals with verified CI evidence.
05 / EVIDENCERun it on GitHub
Actual CI results, command flow, artifacts, and local PowerShell controls.
Engineering by Chandan Vura.
Designed, implemented, tested, and maintained by Chandan Vura. The repository's contributor graph and commit history show authorship. AI assisted with site drafting and code review; the API, pipeline outputs, and claims should be judged against the linked source and live run evidence.