Engineering for Engineering's Sake
summary
Company builds a social feed for a peer-to-peer marketplace (12 million users, €60M funding) and chooses Redis for sorted-set convenience; result increases engagement and sales but creates heavy operational pain — RAM growth, no mature HA then, every-30-minute forks for backups, an open technical-debt ticket from Mar 2014 closed only Sep 2015 after migrating to Redis Cluster. A contemporary competitor uses memcached and ships faster. Lesson: prefer boring, stack-aligned tools and optimize company-wide to reduce future work.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:49MAKE SECOND-HAND THE FIRST CHOICE WORLDWIDE
- 2:01ENGINEERING IS FUN
- 5:56READY TO STUDY SOMETHING SERIOUS
- 6:53WAIT A SEC.
- 8:12AT HOME IS ALWAYS FUN
- 10:35RUBY RAILS MYSQL BACKBONE
- 11:06ELIXIR PHOENIX RETHINKDB REACT
- 12:06I LOVE TO DO ENGINEERING FOR ENGINEERING'S SAKE
- 12:35SAME MINDSET KW AT WORK
- 17:29MARKETPLACE NEEDED A FEED
- 19:26REDIS IS A PERFECT FIT!
- 19:37EDIS SORTED SETS ARE A PERFECT FIT!
- 20:57MEMBERS ARE HAPPY!
- 21:21WHAT ABOUT ENGINEERS?
- 22:29EVERYTHING IN RAM... HIGH AVAILABILITY FORKING EVERY 30MIN
- 24:37MIGRATION TO REDIS CLUSTER SEPTEMBER 2015
- 26:15ETSY CHOSE MEMCACHED
- 29:35TOOLS
- 30:25INFORMATION
- 33:08KNOWLEDGE
- 35:08OPERATIONS
- 37:42SHIPPING
- 40:49THE "RIGHT" TOOL FOR THE JOB
- 41:40USE BORING CODE, TECH, ENGINEERING
related talks
41mEngineering for Engineering's Sake
46mScaling Pinterest
27mEngineering Productivity Starts with Predictable Behaviour
26mBe Awesome By Being Boring
31mBuilding new on top of old: the argument for simplicity
30mArchitecture & Teams at Less-than-Google Scale
18mMaking what you have enough
36mApps, stacks & frameworks: Avoiding "Shiny Object" Syndrome