Santekno
Projects/Merchant Promotion Service & Promotion Aggregator Service Ownership
ByteDance logoPart of ByteDance · Software Engineer, Promotion Platform Team
Backend / APILive

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.

2025-merchant-voucher-ownership · main
# E-Commerce / Promotion
$ go -X POST /2025-merchant-voucher-ownership/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2025-merchant-voucher-ownership.synced
Role
Backend Engineer
Timeline
2025
Team
1
Domain
E-Commerce / Promotion
Stack
4 tech
Status
Live
01

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.

A backend has no screens, so its "UI" is the operational surface: the ops/troubleshooting flow, health dashboards, and cross-team documentation.

Ops view — day-to-day issue handling
Grafana — service health & query performance
Docs & links — technical guidance for teams
03

Problem & Solution

Problem

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.

Solution

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.

04

Workflow

Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.

flowchart diagram

inquiry

troubleshoot

optimize

docs

Other Teams

Service Owner

Merchant Promotion Service

Managed RDS

Technical Guidance

Use case interaction
05

Architecture

flowchart diagram

metrics

Sellers / Teams

merchant-promotion-service

promotion-aggregator-service

Managed RDS

Prometheus / Grafana

System architecture
Architecture notes

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.

state diagram

first point of contact

query / logic fix

guidance shared

reported

triaged

optimized

documented

Issue handling lifecycle
06

Features

Ownership
  • Day-to-day seller-voucher issues
  • First point of contact for other teams
Optimization
  • Slow query optimization
  • Simplified complex logic
Enablement
  • Technical guidance for other teams
  • Documentation for integration
07

Tech Stack

language
Go
database
Managed RDS
observability
PrometheusGrafana
08

Engineering Challenges

01
Fast, confident debugging under ownership

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.

02
Being the reliable point of contact

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.

09

Outcomes

1st
point of contact for other teams
0
unresolved escalations
3
optimization areas addressed
10

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.

11

Related Santekno Tutorials

Interested in working together?

Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.