Scaling Product Hunt from 1 to millions of users

Scaling Product Hunt from 1 to millions of users

How the Product Hunt team was able to scale our systems from 1 user to millions of users. The Talk is focused on our process and technology choices.

7a0e72a6f55811246bb5d9a946fd2e49?s=128

Radoslav Stankov

September 04, 2020
Tweet

Transcript

  1. Radoslav Stankov 04/09/2020 Scaling Product Hunt from 1 to million

    of users
  2. Radoslav Stankov @rstankov blog.rstankov.com
 twitter.com/rstankov
 github.com/rstankov
 speakerdeck.com/rstankov

  3. None
  4. None
  5. None
  6. None
  7. How it all started

  8. An Idea t !

  9. Funding t ⛽

  10. None
  11. Product Hunt + AngelList t #

  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. 2019... t $

  20. None
  21. None
  22. None
  23. Max number of engineers we ever had was 8

  24. image credit: remotehub.io

  25. 3 phases of a startup explore expand extract ...

  26. 3 phases of a startup explore expand extract ... I

    think, we are here %
  27. None
  28. Process

  29. None
  30. None
  31. “Process is automatic decisions for trivial questions and framework for

    making decisions for all other questions.” - Rado What is process?
  32. Our process had changed and continues to evolve, and the

    followings are the constants in our process over the years &
  33. ' single player mode ( automation ) code review *

    constant delivery + maintenance
  34. Single Player Mode

  35. None
  36. None
  37. Project , - . % Testing 2 weeks fixed sprints

    t / 0 1 Project Project Project Project Project
  38. Automation t 2 3 linters - Brakeman, Rubocop, ESLint, Prettier

    ) unit & e2e tests - Ruby, JavaScript + type safety - TypeScript, GraphQL * deployment - CircleCI 4 infrastructure - Terraform 5 monitor & alert
  39. Code review t 4

  40. Code review t 4

  41. Code review t 4

  42. None
  43. Feature flags t 6

  44. OFF ON User Check Feature flags t 6

  45. None
  46. 1st day 4th day 1st week ...

  47. 1st day 4th day 1st week ... developer

  48. 1st day 4th day 1st week ... developer admins

  49. 1st day 4th day 1st week ... developer admins beta

  50. 1st day 4th day 1st week ... developer admins beta

    everybody
  51. None
  52. t 7 Happy Friday 8 fix exceptions 9 database performance

    : upgrade dependancies ; pay technical depth & code migrations < bug fixes
  53. None
  54. We are a startup, we experiment, iterate, and remove what

    doesn't work. Our code needs to be decoupled, so it is easy to add and remove features.
  55. None
  56. = have good defaults > have good code organization ?

    make common operations easy @ isolate dependencies A extensibility and reusability
  57. 2014 2019 2015 2016 2017 Architecture History t B

  58. 2014 2019 2015 2016 2017 Architecture History t B

  59. 2014 2019 2015 2016 2017 Architecture History t B

  60. 2014 2019 2015 2016 2017 Architecture History t B

  61. 2014 2019 2015 2016 2017 Architecture History t B

  62. 2014 2019 2015 2016 2017 Architecture History t B

  63. 2014 2019 2015 2016 2017 Architecture History t B

  64. 2014 2019 2015 2016 2017 Architecture History t B

  65. 2014 2019 2015 2016 2017 Architecture History t B

  66. 2014 2019 2015 2016 2017 Architecture History t B

  67. ...we plan 6 months ahead, assuming we will double our

    targets
  68. None
  69. The monolith(s) t C

  70. Recap

  71. None
  72. None
  73. https://speakerdeck.com/rstankov Thanks ,

  74. None