Founder request → prod in 3 days
HubMarket: marketplace stock sync
Production case of a founder-driven sprint inside HubMarket. A real founder customer requested stock synchronization across three marketplaces (Wildberries, Ozon, Yandex Market). 3 days passed from the first Telegram message to the release.
Timeline
- Day 0Founder request via Telegram, requirements and data format discussion
- Day 1Architecture sketch, data-source investigation across 3 marketplaces, queue choice
- Day 2End-to-end pipeline on one marketplace, test on real data
- Day 3Extended to all 3 marketplaces, load-tested, production release
Decisions made
Playwright over official APIs
Some marketplaces only expose the needed data via UI (or the API is stale/unstable). Playwright + stealth gives a stable path with API fallback where available.
pg-boss as the queue
Already used elsewhere in HubMarket. No reason to add a Kafka/RabbitMQ when existing infra handles it.
Store deltas, not snapshots
Hourly stock snapshots = terabytes. Deltas plus periodic rebase let everything live in Postgres without a separate DWH.
Outcome
- Released to prod on day 3 after the request
- Coverage: 3 marketplaces (Wildberries, Ozon, Yandex Market)
- Request → prod cycle of 3-4 days became a recurring pattern for HubMarket — featured as the 4th metric on the landing
- Backs the Hero promise «MVP в неделю — стартапам» / «MVP in a week — founders»
Stack
Next.jsHonoPlaywrightpg-bossPostgreSQL