PSM Migration for a Merchant Voucher Database
Mentored an intern through a merchant voucher database migration to PSM, then took over ownership of the cutover, database rollback, and QA testing.
- Role
- Backend Engineer / Mentor
- Timeline
- 2025
- Team
- 3
- Domain
- E-Commerce / Infrastructure
- Stack
- 7 tech
- Status
- Live
Overview
This project migrated the merchant voucher database onto PSM. I began as a mentor to an intern based in Yogyakarta — explaining the database structure and service flow, reviewing code, and guiding the cutover plan — and later took over the remaining work, including ownership of the final cutover.
Gallery
A backend has no screens, so its "UI" is the operational surface: the migration/ops flow, the QA test matrix, and the cutover report.
Problem & Solution
Because I started as a mentor rather than a hands-on owner, I had limited context on some flows and documentation. When the intern's tenure ended before completion, I had to absorb the remaining tasks quickly and ensure the database cutover still ran safely.
I maintained close communication with the intern, gave detailed explanations, ran regular code reviews, and guided a structured cutover plan. After the handover I completed the outstanding requirements, managed the database rollback process, and collaborated with the QA engineer on manual, regression, and live testing. I then led the cutover alongside QA and a teammate, dividing responsibilities for a smooth execution.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
The merchant-voucher-service moved onto PSM with resources via the internal serving platform and the internal cloud platform and its data on a managed RDS (relational database), with Prometheus/Grafana for monitoring. The cutover plan included an explicit rollback path, which proved essential when a deployment issue surfaced during release and required an immediate hotfix.
Features
- Intern onboarding on DB & service flow
- Regular code reviews
- Cutover planning guidance
- Took over remaining tasks
- Final cutover ownership
- Database rollback management
- Manual, regression & live testing with QA
- Coordinated cutover execution
Tech Stack
Engineering Challenges
I joined as a mentor rather than a hands-on owner, so after taking over I hit gaps in flows and documentation. Fix: I dug into the sources myself to rebuild context — a reminder to stay engaged from the start when responsibilities can shift.
Some critical steps had not been completed or communicated when the intern's tenure ended, delaying the cutover. Fix: I took ownership, completed the outstanding requirements, and managed the database rollback process.
During cutover we hit a deployment issue that testing had missed. Fix: an immediate hotfix, and a lesson to allocate more time for thorough testing and build more comprehensive test cases for edge scenarios.
Outcomes
Lessons Learned
Staying engaged from the beginning builds the context needed when responsibilities shift. The incomplete handover taught me to verify that every step is truly done and communicated, and the undetected deployment issue reinforced the value of allocating enough time for thorough testing and more comprehensive edge-case coverage.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.