Microservices Explained: Build Scalable Systems!

แชร์
ฝัง
  • เผยแพร่เมื่อ 24 ม.ค. 2025

ความคิดเห็น • 11

  • @mohitsoni3819
    @mohitsoni3819 3 หลายเดือนก่อน

    Great Content Bro 👍. Keep share videos for scaling backend.

  • @shaaboink
    @shaaboink 3 หลายเดือนก่อน

    Awesome explanation

  • @AbhishekYadav-ch2mn
    @AbhishekYadav-ch2mn หลายเดือนก่อน +1

    Waiting for an ecommerce microservice microfrontend project with Kafka, mongodb, redis for cache.

  • @AbhishekYadav-ch2mn
    @AbhishekYadav-ch2mn 2 หลายเดือนก่อน +1

    Can you please make project on microservice & microfrontend? I'll buy even if it's paid!

    • @SWE-with-VivekBharatha
      @SWE-with-VivekBharatha  หลายเดือนก่อน

      Hey there! Thank you so much for your interest! I'm really excited that you'd like to see a project on microservices and microfrontends.
      No need to pay anything - we're here to share knowledge and help out!
      It would be great if you could share a bit more about what you're expecting from the project, maybe with an example of what you're envisioning?
      That way, I can tailor it to what would be most helpful for you.
      And of course, if you enjoy our content, spreading the word about the channel would be great 😊

    • @AbhishekYadav-ch2mn
      @AbhishekYadav-ch2mn หลายเดือนก่อน

      @SWE-with-VivekBharatha ecommerce website with microservice & microfrontend. Redis , Kafka, docker. I have already shared your content with my friends

  • @BLUR7777
    @BLUR7777 3 หลายเดือนก่อน +1

    Sir, what is an API Gateway, and how would the order's database know the user's database information since there's no relation between them?

    • @SWE-with-VivekBharatha
      @SWE-with-VivekBharatha  3 หลายเดือนก่อน

      Great question!
      An API Gateway is like a traffic controller in a microservices system. It handles client requests and routes them to the right service (like the order or user service). It also manages things like authentication, load balancing, and rate limiting (Will create a separate video for API Gateway soon)!
      As for how the order service gets user info without a direct relationship: in microservices, databases are usually isolated for each service.
      So, the order service can call the user service via an API to get the required user details based on user Id.
      Or we can store some meta data like name, email along with user Id in the order details ( Can vary based on many conditions like how often this meta data will change )
      This keeps services independent but still able to communicate when needed!
      Hope this clears your doubt! 😊