Luxury · eDTL
eLADY — eDTL so CSV and Sheets become a partner taxonomy in 3-second cycles.
eLADY has been Japan's #1 online retailer of pre-owned luxury since 1999, Tokyo. Partners still arrive as CSV and Google Sheets. We built eDTL — extract, deduplicate, transform, load — so those dumps land in the partner taxonomy every three seconds, as incremental deltas, not as a nightly batch.
- speed
- +60%
- month saved
- $300
- refresh
- 3s
Tokyo, 1999, still a spreadsheet
eLADY runs eLADY GLOBAZONE (pre-owned luxury), UKEROO (genuine auto parts, with Ecoline / Toyota) and LISUTO! (list once, sell everywhere). Member of the International Anti-Counterfeiting Coalition. The catalogue is serious. The inbound data was not: CSV files and live Google Sheets from partners, each in its own shape.
eDTL, on a three-second clock
We built an Extract → Deduplicate → Transform → Load pipeline. Sources are CSV and Google Sheets. The loop is pseudo-realtime: poll every three seconds, apply only the incremental delta, write the partner taxonomy. Not a nightly job. Not a full reload every time a cell changes.
- Extract from CSV and Google Sheets
- Deduplicate before anything hits the partner map
- Transform into the partner taxonomy
- Load on a 3-second cycle, deltas only
Fastify first, then a Go kernel
Version one was Fastify / Node — enough to prove the loop. The compute kernel — taxonomy convert, mapping, pattern-match — moved to Go. About 60% faster on those steps. The Go core now eats tens of thousands of rows per iteration. Fastify stays in the picture; the heavy work does not.
Technologies
- Fastify
- Go
- SQL
Outcomes
- Taxonomy convert, mapping and pattern-match ~60% faster after the Go rewrite
- New partners plug into the same pipeline instead of a custom one-off
- $300/month saved on the previous integration setup
Recommended articles
Blog
The case for boring web stacks
TypeScript, Postgres and edge deployment are not exciting — they are how you still iterate fast in year three without rewriting the platform.
Blog
Shipping evals before prompts
Why we run regression suites on LLM outputs before every release — and how it changed our AI delivery cadence at ZNN.
Blog
Mobile release trains that do not break
Fastlane, staged rollouts and feature flags — a practical playbook from eighteen App Store submissions without a Friday-night rollback.
Recommended case studies
Luxury · Volume eDTL
The Brand Collector
The Brand Collector resells pre-owned luxury through a supplier network. Same class of problem as a catalogue feed — except each dump crossed 120,000 rows, and the CSV they hold sits above 169,000. Fastify stayed the orchestrator. The heavy compute moved to Go workers. About 60% faster on taxonomy, mapping and pattern-match at that volume.
iGaming · Platform
Casino operator · NDA
Under NDA we stabilised three production gambling brands: cleaned up legacy PHP/JS stacks, extracted shared modules, and shipped a new marketing site without stopping live traffic.
Marketing · Fintech
Digital DAO
Digital DAO is a marketing studio in Belarus that works mostly with fintech. We did not repaint the old site. We rebuilt the story and the visual system so it would sit in a room with banks, not with a carnival agency deck.