gRPC vs REST - KEY differences and performance TEST

Поделиться
HTML-код
  • Опубликовано: 5 июн 2024
  • Let's make a comparison between gRPC and REST, highlighting their unique features and use cases in network communication.
    ▶ Watch next: graphql vs rest - • GRAPHQL vs REST | Shou...
    ▶ Contact Jelvix: jelvix.com
    ▶ For RUclips partnerships: youtube@jelvix.com
    Subscribe for more tech tips and tutorials: / @jelvix
    ▶ Time codes:
    00:00 gRPC vs REST
    00:40 What is REST API?
    01:35 What is gRPC?
    02:45 Summary of comparison
    05:12 Performance test
    06:03 Best practices for API design
    06:44 Watch this next
    ▶ Follow us:
    Facebook - / jelvixcompany
    Twitter - / jelvix
    Instagram - / jelvix
    Linkedin - / jelvix
    ▶ About this video:
    Join us in our latest video where we dive deep into the world of web communication protocols, comparing gRPC with REST. We've designed this video to be both informative and accessible, breaking down complex concepts into understandable segments. You'll discover the unique advantages and potential drawbacks of each protocol, illustrated with real-world examples. Whether you're a seasoned developer or just starting out, this video will enhance your understanding of gRPC and REST, helping you decide which protocol is the best fit for your next project. Tune in for an engaging and enlightening exploration of these two pivotal technologies in modern web development.
    #ai #aitools #programming
    ---
    Disclaimer:
    The content in this video is based on company's experience. The primary purpose of this video is to educate and inform. Note that Jelvix is not responsible for the results of advices that were taken without considering individual situation and goals of your business. Jelvix strongly recommends to perform your own independent research before making any critical decisions. If you have a complaint about something or find your content is being used incorrectly, please contact Jelvix.
    This video is available for private, non-commercial use only. You may not edit or modify this video.
  • НаукаНаука

Комментарии • 14

  • @Jelvix
    @Jelvix  6 месяцев назад +3

    What do you prefer to use more - gRPC or REST? Tell us your opinion on these two... 🤯

  • @JaneMoir
    @JaneMoir 6 месяцев назад +4

    I've been curious about gRPC and REST differences for a while now. This vid was super informative and helped me so much... Thanks! ☺

  • @jiminnovator1556
    @jiminnovator1556 6 месяцев назад +4

    Absolutely loved this comparison! Thanks for shedding light on this topic!

  • @monicasmith6007
    @monicasmith6007 6 месяцев назад +3

    This was eye-opening! Which one, gRPC or REST, would you suggest for IoT applications and why?

  • @jeremypatrick7853
    @jeremypatrick7853 Месяц назад +1

    Perhaps a combination of the two? REST for minimal data that needs to be transported, and any large sets of data using gRPC, isn't that supposed to be the beauty of microservices?

  • @GauriSpirit
    @GauriSpirit 4 месяца назад

    Nice explanation

  • @amirbaha2ri
    @amirbaha2ri Месяц назад

    Consider I just need a simple CRUD and a few actions for my own business and there is no importance how hard is implementing each one of REST or gRPC. Can I choose gRPC just for getting experienced in it, and I can hope will not face any problem that wouldn't happen with REST?

  • @keplerk
    @keplerk Месяц назад +1

    A question would be, how costly it's to keep and maintain grpc compared to a simple rest api.

    • @Jelvix
      @Jelvix  28 дней назад

      Thank you for this question! We'll take it into account in our upcoming videos

  • @fcnealvillangca7943
    @fcnealvillangca7943 3 месяца назад +3

    as new to industry I take Rest API because it's stable. we tried GraphQL but it didn't fix the problem infact it only introduce extra work to the backend. I will just adjust to graphql , grpc, trpc etc etc incase the Job requires to. But what can you suggest

    • @RayParker
      @RayParker Месяц назад

      I found GQL a God send in the Rails world - if you know how to use it. I’ve reduced server loads up to 70% v REST + Rails classic MVC.

    • @RayParker
      @RayParker Месяц назад

      Oh, and back end work quickly declines as the API matures.

  • @davidhunter3605
    @davidhunter3605 Месяц назад +2

    Wow totally meaningless performance tests. What did you measure exactly? How did you measure it? Basically you might as well have produced random numbers as you don't say what you tested.