Promotion & Marketing Tools Support Campaign Scenario
Planned and delivered a complex multi-region campaign scenario in two phases, resolving cross-region routing, timeout configuration, and tag lifecycle integration.
- Role
- Backend Engineer
- Timeline
- 2025
- Team
- 4
- Domain
- E-Commerce / Campaign
- Stack
- 8 tech
- Status
- Live
Overview
The Promotion & Marketing Tools Support Campaign Scenario was a complex initiative spanning multiple cases, cross-service dependencies, and multi-region deployment. I owned end-to-end technical planning and execution, designing the tech plan from scratch and splitting it into two clear phases to control risk and keep delivery predictable.
Gallery
A backend has no screens, so its "UI" is the operational surface: the campaign execution API, multi-region ops, and monitoring dashboards.
Problem & Solution
The scenario involved many interacting cases and cross-service dependencies deployed across multiple regions, where region-specific configurations and cross-region routing could easily cause regressions or environment leakage. Delivering it safely required careful phasing, strict environment isolation, and tight cross-team coordination.
I led the full technical design — defining execution flows, mapping cross-service dependencies early, and setting clear boundaries — then aligned stakeholders through a formal tech review. I ensured independent per-region test coverage, validated pre-production environment isolation and data-center alignment to prevent isolated test environment traffic leaking to Production, and collaborated with the tag-management-service team to jointly debug tag association / tag removal flows. Phase 1 shipped on schedule; for Phase 2 I owned the recovery, resolving the QA blockers.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
campaign-core-service (Go / RPC) drives the scenario, applying timeout configuration and calling tag-management-service for tag lifecycle operations across data centers in multiple regions. Because tag-management-service runs in another region, traffic is routed cross-region, with tag-association / tag-removal permissions explicitly granted and Prometheus/Grafana monitoring in place.
Features
- Two-phase execution design
- Cross-service dependency mapping
- Per-region test coverage
- Pre-production environment isolation & data-center alignment
- Cross-region routing
- tag-management-service tag association / removal
- Timeout config & permission setup
Tech Stack
Engineering Challenges
Each region needed independent, complete test coverage while isolated test environment traffic risked leaking to Production. Fix: enforced data-center alignment and validated pre-production environment isolation, coordinating with QA to avoid region-only regressions.
Phase 2 hit QA blockers from complex flow dependencies: `campaign-core-service` → `tag-management-service` timeouts and traffic needing to reach another region. Fix: raised timeout config, resolved cross-region routing, and updated tag-association / tag-removal permissions.
Correct tag association / tag removal behavior spanned both campaign and tag-management perspectives. Fix: joint debugging with the `tag-management-service` team to verify the full tag lifecycle.
Outcomes
Lessons Learned
I gained hands-on experience with multi-region and cross-region execution, learning that correctness in complex campaigns depends as much on environment and infrastructure control as on business logic. Phased execution proved effective at containing blast radius, and early cross-team communication plus joint debugging were key to resolving system-level bottlenecks — timeout, permission, and routing — rather than applying temporary workarounds.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.