Scaling Slack - The Good, the Unexpected, and the Road Ahead

Поділитися
Вставка
  • Опубліковано 8 лип 2024
  • InfoQ Dev Summit Boston, a two-day conference of actionable advice from senior software developers hosted by InfoQ, will take place on June 24-25, 2024 Boston, Massachusetts.
    Deep-dive into 20+ talks from senior software developers over 2 days with parallel breakout sessions. Clarify your immediate dev priorities and get practical advice to make development decisions easier and less risky.
    Register now: bit.ly/47tNEWv
    ------------------------------------------------------------------------------------------------------------------------------------------
    Video with transcript included: bit.ly/2J3laLP
    Mike Demmer talks about the major changes that Slack has made to the service architecture to meet the needs for larger and larger enterprise customers. Demmer presents 3 of these changes: decomposition of the real-time message service, client-side lazy loading via edge caching, and scaling the primary data storage tier with fine-grained horizontal sharding using Vitess.
    This presentation was recorded at QCon San Francisco 2018: bit.ly/2uYyHLb
    #Slack #Performance #Scalability #InfoQ #QConSanFrancisco
  • Наука та технологія

КОМЕНТАРІ • 10

  • @umamaheshsukamanchi
    @umamaheshsukamanchi 3 роки тому +3

    Very well explained. Thanks

  • @at_tap
    @at_tap 3 роки тому +3

    Great content. There seems to be lot of people in the audience with cough issue, had a hard time to understand few sentences

    • @alexerohin4573
      @alexerohin4573 3 роки тому +1

      It's almost like he's giving this talk in a hospital or something.

    • @foreverursabhi
      @foreverursabhi 2 роки тому +4

      People showing COVID symptoms 2 years before it hit.

  • @tejamenneni1844
    @tejamenneni1844 3 роки тому +1

    How do you add jitter to client to spread out load?

  • @foreverursabhi
    @foreverursabhi 2 роки тому +8

    The audio well downhill at 11:38, and all the coughing isn't helping follow the talk. If you're coughing so much, show some courtesy and leave the room.

  • @RomanScherbatyuk
    @RomanScherbatyuk 5 років тому +1

    did you think about nosql db and akka way approach?

    • @youngboss3659
      @youngboss3659 Рік тому

      In reality, you have to consider cost of engineering work. They added the management & routing layer on top of MySQL database definitely meets the needs. If you look at this problem today, you can just use snowflake to help with this issue

    • @hdrkn5247
      @hdrkn5247 21 день тому

      @@youngboss3659 what is snowflake?