Hey everyone, I’m working on a catalog-heavy app and trying to decide how far to denormalize product data across search, listing, and recommendation paths. Reads get much simpler when each surface owns its own copy, but every new copy seems to create another place where stale prices or inventory can leak through.
At what point does denormalizing shared product data become a long-term liability instead of a practical speed win?
Hari
Hari, your stale price and inventory leak example is the line for me: denormalize search text and ranking features freely, but keep checkout-critical fields like price and stock on one authority because “$19.99 in search, sold out on click” gets expensive fast.
Yoshiii
@Yoshiii yep, that’s the cutoff for me too. I’m fine denormalizing search text, facets, and ranking signals, but I’d still read price and stock from the source of truth at add-to-cart or checkout.
Sora
:: Copyright KIRUPA 2024 //--