A Micro Introduction to Microservices

Поділитися
Вставка
  • Опубліковано 4 лис 2022
  • In this video, we take a high-level look at microservices, what problems they solve and what new problems they introduce. Microservices is a huge topic and this video just surface the surface.
    Here are some other videos about microservices that will help you continue your learning path:
    Monolith vs Microservices: • Monolith vs Microservices
    The Problem With Microservices: • The Problem With Micro...
    🌎 Follow me here:
    Discord: / discord
    Twitter: / tomdoes_tech
    Facebook: / tomdoestech​
    Instagram: / tomdoestech​
    TikTok: / tomdoes_tech
    ☕ Buy me a coffee: www.buymeacoffee.com/tomn
  • Розваги

КОМЕНТАРІ • 34

  • @sidharthmohanty2538
    @sidharthmohanty2538 Рік тому +4

    A project/tutorial will be super helpful too!

  • @sergiyrudenko905
    @sergiyrudenko905 Рік тому +3

    Tom thank you very much! Great video, I hope in the future you can create a lesson on how to build a simple app using microservices. 🙏

  • @umarmuhammadzakari4585
    @umarmuhammadzakari4585 Рік тому +4

    Can't wait for more of these videos Tom.
    Keep it up

  • @shivanshpatel4072
    @shivanshpatel4072 Рік тому +2

    Really Man Amazing video we need a tutorial for How to setup microservices (with real world practices)

  • @lardosian
    @lardosian Рік тому +2

    Takes a swig of a beer from a micro brewery to get started!!

  • @sidharthmohanty2538
    @sidharthmohanty2538 Рік тому +2

    Amazing!!!!

  • @pranav7478
    @pranav7478 Рік тому +1

    Explain well tom :)

  • @shihabunshakib5740
    @shihabunshakib5740 Рік тому +2

    Really like to a project on microservices..

  • @noyou174
    @noyou174 Рік тому +2

    Best programming channel on youtube ❤️

  • @sidwebworks9871
    @sidwebworks9871 Рік тому +2

    Amazing video 🥂❤️

  • @techworld3043
    @techworld3043 Рік тому +1

    great video

  • @NathanielBabalola
    @NathanielBabalola Рік тому +1

    Awesome

  • @santanudash2488
    @santanudash2488 Рік тому +1

    Great

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

    Are we also doing an end to end project?

  • @ricko13
    @ricko13 Рік тому +1

    I know you got a huge mic right there but the audio sounds like it was recorded with the camera built-in mic (low quality)

  • @santanudash2488
    @santanudash2488 Рік тому +1

    At the BFF layer can we use node while backend is spring boot

    • @TomDoesTech
      @TomDoesTech  Рік тому +1

      Yeah of course! That's the benefit of microservices. You don't need a BFF, but it makes things a lot easier

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

    Is this for frontend or backend ?

  • @elab4d140
    @elab4d140 Рік тому +1

    didn't understand the BFF part very well, is it like an api gateway to the microservices or it is just a proxy between the backend and the ui

    • @TomDoesTech
      @TomDoesTech  Рік тому +2

      The BFF layer sits between the services and the UI, it would sit behind an API gateway

  • @Dipesh_Sol
    @Dipesh_Sol 24 дні тому

    As per the diagram, BFF looks like a single point of failure. Even if scale it vertically and add a load balancer, it still looks like we're missing out on the advantage of individual scaling in a microservices architecture. Can you explain more on these concerns?

    • @TomDoesTech
      @TomDoesTech  24 дні тому

      You can scale the BFF horizontally, it's just another application like any of the services

    • @Dipesh_Sol
      @Dipesh_Sol 24 дні тому

      ​@@TomDoesTech thanks for the quick response. let's say we have a sudden spike for products microservice, without BFF we can just scale that up and down. With BFF we have to scale BFF which deals with different types of request. Hence, losing the Advantage of individual scaling in a microservice architecture

    • @Dipesh_Sol
      @Dipesh_Sol 24 дні тому

      I also went ahead to read more about BFF on AWS and it suggested it's a design pattern instead of a single service. It can be seen as an abstraction for multiple components like Api gateway, cognito, dynamo dB, lambda and event consumers all collectively called BFF. This makes it a bit confusing for me when you say it's just another service.

    • @TomDoesTech
      @TomDoesTech  24 дні тому

      @@Dipesh_Sol I'm not sure what the issue is. The BFF is a part of your service, if it needs to scale up it can. Don't think of it in terms of types of requests, think of it as units of business logic and service the UI is a unit of business logic. Also, just because the products service needs to scale, doesn't necessarily mean the BFF has to as well. Finally, you don't have to have a BFF, but it makes the whole thing a lot easier. Don't think you have to follow all the rules, do what's right for your product and customers.

  • @alvarorenesanchezserrano3040

    is BFF similar to API Gateway?

    • @TomDoesTech
      @TomDoesTech  Рік тому +1

      Nope. The BFF layer will sit behind the API gateway. The API gateway is the access point from the internet into your VPC

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

    too much complexity even for a mid tier app ..heck you might spend more time thinking bout and building the communication layer for these services than actual app.

    • @TomDoesTech
      @TomDoesTech  Рік тому +1

      Well yeah, that's why you only move to this architecture when you have to