Elasticsearch Deprecation & Voucher Platform Migration
Deprecated Elasticsearch for voucher services and migrated to the voucher platform, cutting latency from ~300ms to 100ms with a concurrent worker pool and a dual-layer cache.
- Role
- Backend Engineer
- Timeline
- 2025
- Team
- 2
- Domain
- E-Commerce / Infrastructure
- Stack
- 8 tech
- Status
- Live
Overview
This project deprecated Elasticsearch — which was used solely for voucher-related services — and migrated those reads to the voucher platform. I ran a minimal-effort technical assessment, redesigned the access flow, and introduced performance improvements that cut request latency from roughly 300ms to 100ms.
Gallery
A backend has no screens, so its "UI" is the operational surface: latency dashboards, the query API, and the cache/worker-pool flow.
Problem & Solution
Maintaining Elasticsearch only for voucher lookups consumed unnecessary resources for a dependency that was becoming obsolete. Reading directly from source data risked higher latency, so the flow needed to be both leaner in resource usage and faster for callers.
I migrated voucher reads to the voucher platform and introduced a concurrent worker pool so unrelated data could be fetched asynchronously, backed by a dual-layer cache (Memcached + Redis). Together these reduced latency from ~300ms to 100ms while removing the redundant search infrastructure.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
voucher-service first checks the Memcached and Redis layers; on a miss it fans work out to a concurrent worker pool that reads source data from the voucher platform (hosted on the internal serving platform) in parallel, then populates the cache before responding. Prometheus/Grafana track the before/after latency profile across the migration.
Features
- Concurrent worker pool
- Dual-layer cache (Memcached + Redis)
- Async access to unrelated data
- Elasticsearch deprecation
- Migration to the voucher platform
- Migration to the internal serving platform
- Post-migration edge-case handling
Tech Stack
Engineering Challenges
Removing Elasticsearch meant reads had to hit source data directly. Fix: a concurrent worker pool to fan out unrelated reads asynchronously plus a dual-layer Memcached + Redis cache, taking latency from ~300ms down to 100ms.
Elasticsearch was kept only for voucher use and was becoming obsolete. Fix: a minimal-effort assessment to redesign the flow to read directly from the voucher platform, removing redundant infrastructure and its resource cost.
Problems surfaced only after the migration to the internal serving platform, despite an initial assumption that everything was resolved. Fix: more comprehensive assessment and edge-case handling to stabilize the service post-cutover.
Outcomes
Lessons Learned
This was my first hands-on experience designing concurrent processes across multiple resources, and it grew my interest in performance and concurrency. The serving-platform migration also taught me to anticipate edge cases — issues appeared only after cutover — so thorough, forward-looking assessment matters as much as the optimization itself.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.