MVC Chip-In — Subsidized Voucher Filters
Designed and shipped chip-in (co-funded subsidy) voucher filters for the merchant voucher platform — a database and dataflow architecture with an async message-queue publisher/consumer across two services, aligned with five cross-functional teams and launched for a major anniversary campaign.
- Role
- Senior Backend Engineer
- Timeline
- 2023
- Team
- 5
- Domain
- E-Commerce / Promotion & Discounts
- Stack
- 9 tech
- Status
- Live
Overview
The MVC Chip-In project introduced chip-in filters — co-funded subsidy filters on the merchant voucher platform — that let selected sellers receive platform subsidies on their vouchers during a major anniversary campaign. As the technical lead, I owned the design, database and dataflow architecture, delivery, and cross-team coordination, and guided three new engineers and an intern through the build.
Gallery
A backend has no screens, so its "UI" is the operational surface: the chip-in filter API contract, the subsidy configuration flow, and voucher chip-in dashboards.
Problem & Solution
The merchant voucher platform needed to support subsidized vouchers for a curated set of sellers, driven by campaign filters, with the subsidy application flowing reliably across service boundaries. Without a clean data model and an async pipeline, subsidy state would drift between services, and cross-team dependencies would stall the launch of a major anniversary campaign.
I designed the chip-in filter model end to end: the database schema for subsidy relations and seller eligibility, the dataflow architecture linking the merchant voucher service to a downstream budget consumer service through an async message-queue publisher/consumer, and the API contracts consumed by the seller console and campaign operations. I debugged the publisher and consumer sides in tandem to keep subsidy state consistent, coordinated with five cross-functional teams, and communicated periodically with the campaign team on PRD and TRD milestones. The feature shipped end-to-end in staging first, then launched for a major anniversary campaign, with roughly 98% of the collaborative scope completed with the campaign team.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
The merchant voucher service owns voucher creation and lifecycle and delegates subsidy resolution to a chip-in subsidy filter service backed by a Managed RDS. Once a chip-in voucher is configured, the voucher service publishes a subsidy event to a message queue; a budget consumer service consumes the event, applies the subsidy, and reconciles the budget — keeping the subsidy path fully asynchronous. Voucher and subsidy tables are modeled as first-class relations so filters, contribution splits, and lifecycle transitions are queryable. Prometheus and Grafana track chip-in voucher growth and redemption quality.
Features
- Chip-in filter definition & seller eligibility
- Subsidized voucher creation for selected sellers
- Platform/seller contribution resolution
- Database design for subsidy relations
- Dataflow architecture for chip-in subsidies
- Async message-queue publisher/consumer across two services
- End-to-end staging build & self-test coverage
- Cross-functional alignment with a campaign team
- Guidance for junior engineers and an intern
Tech Stack
Engineering Challenges
Subsidy application had to flow asynchronously between the voucher service (publisher) and a budget consumer service (consumer) without dropping or duplicating events. Fix: a message-queue publisher/consumer contract with idempotent handling, debugged across both services in tandem so subsidy state stayed consistent under load.
Chip-in touched promotion, catalog, broadcast, image generation, and workflow-processing ownership at once, with a campaign team as the primary partner. Fix: periodic PRD/TRD sync with the campaign team, clear interface contracts per boundary, and staged rollout — landing roughly 98% of the collaborative scope on time.
Chip-in needed subsidy filters, seller eligibility, and contribution splits to be first-class rather than ad-hoc fields, or the follow-up work would fragment. Fix: a dedicated database design and dataflow architecture so filters, subsidies, and voucher lifecycle events were queryable and extensible across services.
Outcomes
Lessons Learned
Investing in a clean database and dataflow design paid off directly during a high-pressure anniversary campaign: chip-in voucher volume grew 4x after launch and redemption on recommended chip-in vouchers ran 2x higher than on non-recommended ones. Debugging an async publisher/consumer path is easier when both services share the same idempotency and ordering assumptions — and leading a project this broad is as much about aligning five cross-functional teams and mentoring newer engineers as it is about the code.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.