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

    Design Microservice Architectures the Right Way

    InfoQ

    2 HN recommenders · recommended in 3 months, 2019–2021

    YouTube

    48:30 · 741K views · Oct 23, 2018

    Michael Bryzek of Flow gives a QCon London 2018 talk on key decisions for building maintainable microservices. It covers infrastructure, continuous deployment, communication, event streaming and language choice.

    HN commenters recommend it for showing the tooling possible when schemas and APIs are treated as code.

    Software Engineering & LanguagesSoftware architecture & designCloud, DevOps & reliability
    1. 53:14
      Mastering Chaos - A Netflix Guide to MicroservicesInfoQ2.3M views • 9 years ago
    2. 1:00:19
      How To Design A Good API and Why it MattersGoogle TechTalks453K views • 19 years ago
    3. 1:02:50
      The Language of the System - Rich HickeyClojureTV174K views • 13 years ago
    4. 4:57
      Rich Hickey rants about HttpServletRequest in 1080p: Death By Specificity from Clojure Made SimpleFred Overflow43K views • 6 years ago
    5. 54:52
      Introduction to NoSQL • Martin Fowler • GOTO 2012GOTO Conferences1M views • 13 years ago
    6. 54:25
      Event Sourcing • Greg Young • GOTO 2014GOTO Conferences102K views • 11 years ago
    7. 59:50
      Leslie Lamport: Thinking Above the CodeMicrosoft Research403K views • 12 years ago
    8. 49:54
      The Clean Architecture in PythonNext Day Video114K views • 12 years ago
    9. 36:18
      "Data Driven UIs, Incrementally" by Yaron MinskyStrange Loop Conference20K views • 8 years ago
    10. 42:20
      "Stop Rate Limiting! Capacity Management Done Right" by Jon MooreStrange Loop Conference41K views • 9 years ago
    11. 43:39
      CRDTs and the Quest for Distributed ConsistencyInfoQ68K views • 8 years ago
    12. 48:04
      Greg Young — A Decade of DDD, CQRS, Event SourcingDomain-Driven Design Europe190K views • 10 years ago
    13. 1:16:14
      Spec-ulation Keynote - Rich HickeyClojureTV136K views • 9 years ago
    14. 1:06:24
      Rich Hickey: Deconstructing the DatabaseInfoQ106K views • 14 years ago
    15. 1:04:04
      Overwatch Gameplay Architecture and NetcodeGDC Festival of Gaming196K views • 7 years ago
    16. 1:03:48
      Greg Young - CQRS and Event Sourcing - Code on the Beach 2014Code on the Beach170K views • 12 years ago
    17. 45:27
      Avoiding Microservice Megadisasters - Jimmy BogardNDC Conferences439K views • 9 years ago
    18. 1:01:39
      "Simple Made Easy" - Rich Hickey (2011)Strange Loop Conference220K views • 5 years ago
    19. 50:06
      The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017GOTO Conferences677K views • 9 years ago
    20. 1:14:52
      Effective Programs - 10 Years of Clojure - Rich HickeyClojureTV176K views • 9 years ago

    3 comments from Hacker News

    1. @gravypodOct 2020· in “Application Load Balancers enables gRPC workloads with end to end HTTP/2 support”

      My main reasons: 1. It's standardized all the implementation for each language is roughly similar and has the same feature sets (middlewares, stubs, retry, hedging, timeouts, deadlines, etc). 2. High performance framework/webserver in "every" language. No more "should I use flask or the built in http server or gunicorn or waitress or..." 3. Tooling can be built around schemas as code. There's a great talk that I highly recommend about some of the magic you can do [0]. 4. Protos are great for serialization and not just over a network! Need to store configs or data in a range of formats (json, prototxt, binary, yaml)? 5. Streaming. It's truely amazing and can dramatically reduce latency if you need to do a lot of collection-of-things or as-soon-as-x processing. 6. Lower resource usage. Encoding/decoding protos is faster then encoding and decoding json. At high throughput that begins to matter. 7. Linting & standards can be defined and enforced programatically [1] 8. Pressures people to document things. You comment your .c or .java code, why not comment your .proto? [0] - this video [1] - [LINK]

      Strongly recommendsView on HN
    2. @bpicoloMay 2021· in “Smithy: A language for defining services and SDKs”

      Reminds me a lot of this talk: this video I think it's a really powerful paradigm. I think an org adopting such patterns widespread leads to some really rad capabilities. GDPR compliance, for example, is really tough in SOA architectures in companies without a ton of engineering capacity, but this sort of data/api introspection could do a lot to change that. Any plans to open source projection for languages other than Java? edit: I see that typescript and rust are available on github as well

      RecommendsView on HN
    3. @zobiaJul 2019· in “Ask HN: Who is hiring? (July 2019)”

      Flow.io (Flow Commerce) | Hoboken, New Jersey | Dublin, Ireland - [LINK] Flow is a next generation solution for cross-border commerce. Backed by Bain Capital Ventures, Flow has built an API-first, turn-key solution that has been transforming how brands localize their site and sell cross-border. Flow integrates into existing e-commerce platforms and provides brands with a high degree of flexibility over all aspects of the customer experience (local currency pricing, duty & tax calculation, local merchandising), local checkout (local payment methods, local language) and cheap/fast international shipping options resulting in steep growth in international sales. Our dream is to remove borders from global commerce. We are building a point-to-point global eCommerce platform that enables brands to expand internationally. We help brands with everything from catalog management, pricing, currency risk, payment processing, to logistics. The business was founded by Mike Bryzek (co-founder/CTO of e-commerce giant, Gilt Groupe) and Rob (founder/CEO of leader in customer experience, Fizzback). Our approach to software is pretty unique and offers great opportunities to learn. We are a microservices architecture (Scala backends, ReactJS frontends), practice API-first software development, and run continuous delivery (merging a PR deploys the change). You can find more on our approach to software delivery here ( [LINK] ) and on YouTube ( this video ) (100k+ views and counting!) Current open roles

      CitesView on HN