How technology driven B2B disruption works
summary
A B2B ecommerce build handles 500 million products across vendors, replaces Redis/Postgres by using Elasticsearch as single source of truth, and cuts data duplication so global distribution and sync complexity drop. A prototype takes two engineers two days to hit 95% of use cases, then 1.5 weeks to finish edge cases; one-person experiments and a one-day prototype also validate using ES as a key-value store. The change works after ~five man‑years of prior work.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:38VUCA VOLATILITY UNCERTAINTY COMPLEXITY AMBIGUITY
- 10:15YOU NEED INNOVATIVE SYSTEM SOLUTIONS TO USE THESE TECHNOLOGIES
- 10:34DISRUPTION IN SOFTWARE DEVELOPMENT
- 13:20WHAT DO SEWING MACHINES HAVE TO DO WITH B2B DISRUPTION?
- 15:12IMPLEMENTAION OVER CONFIGURATION
- 16:35CASE STUDY THE 500 MILLION PRODUCTS PROJECT
- 20:25BYPASSING RELATIONAL DATABASE
related talks
49mReplatforming Online Search for a Major High Street Retailer
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
33mBuilding an Elastic, Resilient Data Layer to Power New Retail Experiences
26mFrom code to commerce: Engineering’s role in driving business growth
45mPlatform Engineering: Lessons from the Rise and Fall of eBay
38mScaling an online search engine to thousands of physical stores
32mDiscover the Modern Way to Build Real-Time Analytics Solutions at Any Scale
28mGuerilla Tactics for Building Scalable E-Commerce Services with Apache Cassandra, Apache Pulsar, and Vector Search