Merchant Promotion Service & Promotion Aggregator Service Ownership
Owned the merchant-promotion service and promotion-aggregator service day-to-day — handling seller-voucher issues, optimizing slow queries, and acting as first point of contact for other teams.
- Role
- Backend Engineer
- Timeline
- 2025
- Team
- 1
- Domain
- E-Commerce / Promotion
- Stack
- 4 tech
- Status
- Live
Overview
As the owner of the merchant-promotion service and promotion-aggregator service, I handled day-to-day operations for the seller-voucher functionality, kept the codebase healthy, and served as the first point of contact for other teams working with the service.
Gallery
A backend has no screens, so its "UI" is the operational surface: the ops/troubleshooting flow, health dashboards, and cross-team documentation.
Problem & Solution
An owned service needs to stay reliable and easy to reason about: day-to-day seller-voucher issues had to be resolved quickly, slow queries and overly complex logic degraded efficiency, and other teams regularly needed accurate answers to integrate or troubleshoot.
I resolved day-to-day issues, optimized slow queries, improved inefficient use cases, and simplified complex logic in the codebase. I acted as the first point of contact for other teams and provided clear technical guidance and documentation so they could integrate or extend the service confidently.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
merchant-promotion-service and promotion-aggregator-service sit over a managed RDS (relational database) with Prometheus/Grafana for health and query-performance visibility. Keeping the code understandable and the documentation structured meant issues could be traced quickly, and query and use-case optimizations kept the service efficient under day-to-day load.
Features
- Day-to-day seller-voucher issues
- First point of contact for other teams
- Slow query optimization
- Simplified complex logic
- Technical guidance for other teams
- Documentation for integration
Tech Stack
Engineering Challenges
When issues arise, tracing code and finding relevant documentation quickly is critical. Fix: I kept the codebase understandable and the documentation well-structured so issues could be located and hotfixed without delay.
Other teams frequently needed help integrating or troubleshooting the service. Fix: I stayed responsive, explained details clearly, and shared the right information to keep cross-team collaboration fast and effective.
Outcomes
Lessons Learned
Well-structured documentation and clean, readable code are what make debugging and timely hotfixes possible when issues arise. I also learned the value of being fast, helpful, and communicative as a service owner — taking time to explain clearly builds strong cross-team collaboration.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.