Teman Mudik 2026
Route-aware personalization for the holiday travel season.
Backend Developer | 2024 - Present
Backend systems behind national campaigns, contests, and recommendation engines: the problem, what I built, and how it held up.
Led backend delivery for Teman Mudik 2026 by building reusable campaign modules, tightening publish workflows, and hardening high-traffic endpoints during peak holiday windows.
Teman Mudik required rapid content updates close to peak departure dates, while traffic patterns were highly bursty and difficult to predict.
I split the campaign logic into reusable modules for the listing, detail, and CTA tracking endpoints, so each new page variant did not need a backend built just for it.
To keep response time stable, I applied Redis caching for high-read routes and introduced explicit invalidation hooks in publishing flows.
I also worked out the release checklist with QA and DevOps, so shipping an update close to peak traffic stayed a controlled decision rather than a gamble.
Key impact
- Standardized campaign components so editorial and product teams could launch new pages with fewer backend changes.
- Reduced repeated database pressure by introducing route-level cache keys and cache invalidation rules in Redis.
- Made releases during traffic peaks less risky, through staging parity checks and deployment runbooks the team could follow.
Technologies used
- PHP
- Phalcon
- PostgreSQL
- Redis
- Nginx