Masterclass | Tackling the Hidden Time Cost in HTTP Clients

Sdílet
Vložit
  • čas přidán 25. 02. 2024
  • In this masterclass, we unravel the complexities surrounding HTTP clients, providing developers and technical leaders with actionable insights to overcome challenges and revolutionize their development processes.
    Download the slides by filling in the form on this page: platformatic.dev/events/httpc...
    00:59 Introduction
    02:18 Axios vs Got vs Node-fetch vs Request vs Undici
    03:39 Comparison of libraries
    10:32 Why choose Undici?
    13:10 Why undici.request?
    14:17 How to make a final decision on which library to use?
    19:25 Undici design principles
    20:15 What is a dispatcher?
    23:09 Mocking requests
    23:29 Handlers
    25:32 Retry agents
    26:42 Interceptors
    27:00 Automatic OIDC tokens & how they work
    33:11 Wy is fetch() slow?
    35:17 HTTP is the best standard interface
    36:02 Can we use Undici dispatchers to implement networkless HTTP?
    36:15 Injecting an HTTP request into a Node.js server
    38:10 What is Platformatic & how can it help you?
    41:45 Platformatic Client Demo
    1:00:00 Q&A
  • Věda a technologie

Komentáře • 4

  • @tusharbarate4973
    @tusharbarate4973 Před 5 měsíci +1

    You talked about load balancing? Is there any documenation in undici?

    • @platformatic
      @platformatic  Před 5 měsíci

      There is a BalancedPool that you can use: undici.nodejs.org/#/docs/api/BalancedPool

  • @tusharbarate4973
    @tusharbarate4973 Před 5 měsíci

    Difference between client.request and undici.request and undici.dispatch is not clear, when to use what?

    • @platformatic
      @platformatic  Před 5 měsíci +1

      client.request() routes the request using the underlining socket of the client. undici.request uses the global dispatcher. You probably don't want to use the dispatch methods unless for some really advanced behaviors.