Santekno
Projects/Feature Unification & Legacy Feature Sunset
ByteDance logoPart of ByteDance · Software Engineer, Promotion Platform Team
Backend / APILive

Feature Unification & Legacy Feature Sunset

Unified seller promotion features with the e-commerce platform's seller-promotion capability and safely sunset the legacy promotion tools with near-zero defects.

2024-mvc-unify-sunset · main
# E-Commerce / Promotion Tools
$ go -X POST /2024-mvc-unify-sunset/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2024-mvc-unify-sunset.synced
Role
Backend Engineer (Main POC / Owner)
Timeline
2024
Team
4
Domain
E-Commerce / Promotion Tools
Stack
8 tech
Status
Live
01

Overview

Feature Unification & Legacy Feature Sunset was an initiative to consolidate seller promotion features onto the e-commerce platform's seller-promotion capability and retire the older, divergent promotion tooling. I served as the main point of contact and owner from the initial technical design phase, defining requirements and architecture under a tech lead's leadership, and delivering the backend needed to unify the feature and sunset the legacy tools.

A backend has no screens, so its "UI" is the operational surface: the unified promotion API, the migration/sunset flow, and adoption dashboards.

API contract — unified promotion configuration
Ops view — migration & legacy sunset flow
Grafana — feature adoption and health
03

Problem & Solution

Problem

Seller promotions were split across the e-commerce platform's native capability and a set of legacy promotion tools with diverging behavior. This fragmentation increased maintenance cost and confused adoption. The features needed to be unified onto a single capability, and the legacy tools needed to be sunset safely — without hurting feature adoption or disrupting sellers.

Solution

I assessed the project needs and produced the TRD (Technical Requirement Document) and logic architecture. I evaluated the e-commerce platform's seller-promotion capabilities, then developed the changes required to adjust and support the feature in alignment with the Product team. I mapped legacy configuration onto a unified schema across promotion-service, seller-promotion-service, and merchant-promotion-service, drove a feature-flagged cut-over, and collaborated with fellow engineers and an intern who joined the project.

04

Workflow

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

flowchart diagram

configure promotion

unified request

route

apply on

sunset

Seller

Seller Console

Promotion Service

Seller Promotion Service

E-Commerce Platform

Legacy Promotion Tools

Use case interaction
sequence diagram
E-Commerce PlatformSeller Promotion ServicePromotion ServiceSeller ConsoleE-Commerce PlatformSeller Promotion ServicePromotion ServiceSeller Consolesubmit promotion configvalidate + map to unified schemaforward unified requestapply promotionconfirmationresult summary
Sequence flow
05

Architecture

flowchart diagram

sunset

metrics

Seller Console

Promotion Service

Seller Promotion Service

Merchant Promotion Service

E-Commerce Platform

Legacy Promotion Tools

Prometheus / Grafana

System architecture
Architecture notes

promotion-service receives unified promotion configuration from the seller console, validates it, and maps it to a unified schema before routing to seller-promotion-service, which applies promotions on the e-commerce platform. merchant-promotion-service handles related merchant-side flows. The legacy promotion tools were sunset behind the same service boundary once cut-over completed. All flows are observed with Prometheus/Grafana.

state diagram

TRD approved

feature parity built

cut-over complete

legacy tools retired

assessed

designed

unified

migrated

sunset

Feature migration lifecycle
06

Features

Seller
  • Unified promotion setup aligned with the e-commerce platform
  • Promotion configuration adjustments
  • Feature parity with the platform's seller-promotion capability
Operations
  • Legacy promotion tool sunset
  • Safe migration & cut-over handling
System
  • TRD & logic architecture
  • Generic service integration (`promotion-service`, `seller-promotion-service`)
  • Prometheus/Grafana monitoring
07

Tech Stack

language
Go
framework
RPC frameworkHertz
protocol
RPCHTTP
database
Managed RDS (relational database)
observability
PrometheusGrafana
08

Engineering Challenges

01
Reaching feature parity across platforms

The unified feature had to match the e-commerce platform's seller-promotion capability without regressions. Fix: a TRD-driven logic architecture and careful mapping to a unified schema, validated with the Product team before build.

02
Sunsetting legacy tools without disruption

The legacy promotion tools were still in active use, so retiring them risked breaking adoption. Fix: a phased cut-over with feature-flagged rollout and close monitoring, so the legacy tools were retired with no major incidents.

03
Keeping quality high with a lean team

Delivery spanned `promotion-service`, `seller-promotion-service`, and `merchant-promotion-service` with a small team including an intern. Fix: clear ownership boundaries, mentoring, and broad self-testing that surfaced only 3 bugs pre-release and none after.

09

Outcomes

3→0
pre → post-release bugs
0
major sunset incidents
high
feature adoption
10

Lessons Learned

Sunsetting a legacy system is as much about sequencing as code: a clear TRD, feature parity validated with Product, a feature-flagged cut-over, and close monitoring let us retire the legacy tools with no major incidents while sustaining strong adoption. Maintained strong feature adoption with significant monthly GMV penetration, and shipped with only 3 bugs found pre-release and none reported afterward.

11

Related Santekno Tutorials

Interested in working together?

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