Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Mastering Chaos - A Netflix Guide to Microservices

    InfoQ

    3 HN mentions · mentioned in 3 months, 2020–2021

    YouTube

    53:14 · 2.3M views · Feb 22, 2017

    A QCon talk from Netflix on running a large microservices architecture and building resilience into it. It touches on tooling such as Hystrix and circuit breakers.

    Mentioned as a real-world example that microservices can work at scale, though commenters are lukewarm and unsure it matches what they remember.

    Software Engineering & LanguagesSoftware architecture & designDistributed systemsCloud, DevOps & reliability
    1. 48:30
      Design Microservice Architectures the Right WayInfoQ741K views • 8 years ago
    2. 45:27
      Avoiding Microservice Megadisasters - Jimmy BogardNDC Conferences439K views • 9 years ago
    3. 1:22:45
      Building Software Systems At Google and Lessons LearnedStanford257K views • 15 years ago
    4. 42:20
      "Stop Rate Limiting! Capacity Management Done Right" by Jon MooreStrange Loop Conference41K views • 9 years ago
    5. 28:21
      Velocity 2012: Richard Cook, "How Complex Systems Fail"O'Reilly60K views • 14 years ago
    6. 52:41
      Seattle Conference on Scalability: YouTube ScalabilityGoogle TechTalks30K views • 19 years ago
    7. 52:29
      "I See What You Mean" by Peter AlvaroStrange Loop Conference59K views • 11 years ago
    8. 46:39
      What I Wish I Had Known Before Scaling Uber to 1000 Services • Matt Ranney • GOTO 2016GOTO Conferences334K views • 10 years ago
    9. 1:10:23
      "Systems that run forever self-heal and scale" by Joe Armstrong (2013)Strange Loop Conference86K views • 5 years ago
    10. 46:15
      AWS re:Invent 2014 | (SPOT302) Under the Covers of AWS: Its Core Distributed SystemsAmazon Web Services10K views • 11 years ago
    11. 58:17
      Raft lecture (Raft user study)Diego Ongaro87K views • 13 years ago
    12. 1:19:35
      Lecture 1: IntroductionMIT 6.824: Distributed Systems924K views • 6 years ago
    13. 1:08:17
      How We've Scaled DropboxStanford372K views • 14 years ago
    14. 1:06:08
      Scaling the Linear Sync EngineLinear37K views • 3 years ago
    15. 1:06:34
      Paxos lecture (Raft user study)Diego Ongaro114K views • 13 years ago
    16. 40:20
      "Testing Distributed Systems w/ Deterministic Simulation" by Will WilsonStrange Loop Conference56K views • 12 years ago
    17. 43:39
      CRDTs and the Quest for Distributed ConsistencyInfoQ68K views • 8 years ago
    18. 56:19
      MINIX 3: a Modular, Self-Healing POSIX-compatible Operating SystemFOSDEM90K views • 16 years ago
    19. 14:36
      Distributed Systems 1.1: IntroductionMartin Kleppmann383K views • 6 years ago
    20. 34:52
      Liberating Distributed Consensus - Heidi HowardReactive Summit6.9K views • 7 years ago

    3 comments from Hacker News

    1. @woutr_beJan 2021· in “Rails, React, Microservices and Micro-FrontEnds”

      > This is unavoidable for many companies, since the code bases are far to large for any single person to grasp them all. That's true, but this was the takeaway from the entire article: > "When we remove that feeling of “I need to know how allllll of this works, but just enough so that I can rescue it when it breaks”, we facilitate the mental room to iterate on our team’s systems with greater depth." To me it sounds like they've now introduced exactly that feeling with micro-services, developers now need to know how all services and front-ends work, and how they interact with each other. Maybe the article is poorly structured, but if that's the entire takeaway from moving to micro-services and micro-frontends, then I do question their choice. > Netflix this video Netflix is indeed one example. It's hard to argue it doesn't work, but from my experience, it never worked out the way it was envisioned.

      CitesView on HN
    2. @dathinabMar 2020· in “Data-Oriented Architecture”

      I think that one was good: - [LINK] I wasn't able to find any other talk I watched back then or any of the stuff I did read, but I then last time I looked into talks and reading material about this was ~2.5 Years ago and while a lot of new software and tooling was done since then the principles didn't change. Try some of the other GOTO; talks about it if you like listening to talks, they tend to be quite good. This was interesting as far as I remember but not what I was looking for: - this video

      CitesView on HN
    3. @kevin_nisbetDec 2021· in “Summary of the AWS Service Event in the Northern Virginia (US-East-1) Region”

      Netflix was talking alot about circuit breaks a few years ago, and had the Hystrix project. Looks like Hystrix is discontinued, so I'm not sure if there are good library solutions that are easy to adopt. Overall I don't see it getting talked about that frequently... beyond just exponential backoff inside a retry loop. - [LINK] - this video I think talks about Hystrix a bit, but I'm not sure if it's the presentation I'm thinking of from years ago or not.

      CitesView on HN