วีดีโอ

No bro... the salary will be low and there is no guarantee that front-end developer role will exist or not

Not really worth it unless you are aiming for a VERY good product company. Agree with @HishamLearns said low salary and opportunities in the normal job market. I would highly recommend to - focus fully on backend - then if you still feel you want to do frontend then expand your profile to Full Stack Developer Which adds more weightage and opportunities in terms of job market. Hope this helps 😊

Thank you 😊

Thanks for the suggestion, will consider it soon!

Appreciate the support 🙌🏻

Thank you 😊

Thank you for the support 😊

Yes am planning a follow up video on database connections and repository pattern

Thanks for the info, will plan

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 😊

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

Thank you 😊

Sure, am dropping a community post on crash courses. Also I dropped a crash course on protocol buffer if you are interested do checkout 😉

In this video, we demonstrate how gRPC functions are invoked. These functions can be triggered in various ways, such as from a REST API on the frontend, which communicates with a microservice. From there, gRPC can be used for all inter-service communication. Additionally, gRPC can be triggered by cron jobs or other background processes, depending on the specific business domain and use case.

@@aabhishakemishra will plan it to cover few features with nestjs.

yep, will share soon as a post.

@@Petrichor1314 thank you 🙌🏻

I am using obsidian not the cloud platform, I will plan to share it as community post may be like an image. Hope that helps!

@@SWE-with-VivekBharatha sounds good

@@iranna9065 this means a lot!! thank you 🙌🏻

@@maheshmagi619 thank you 🙌🏻

@@XronTrix10 thank you so much 🙌🏻 This made by day in mentioning sub count 🥺:)

@@hruthikks1610 Thank you! 😊 You would be surprised if you search like this in google: ‘"API_KEY" "query parameter" documentation’ 😅

In short yes - but not necessarily needed to build full actual complex project. You can start with a very basic server with 2 different services (even one http endpoint is enough which do some iops with a database), use load testing tools like k6 to simulate traffic, from there rest of all the modules you can spin in docker containers. CDN and Data centers exposure would be a bit tricky that you need to deploy into one of cloud service providers like aws, gcp, azure etc I hope this helps, create a repo and start building it, happy to help and contribute! 😊

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! 😊

Good question! In short: yes, 2 separate db queries ( 2 IOPs ) Assuming lets say, the use case is to display on frontend, - we can use 2 separate API requests one for count and other one to get only a set of records with pagination concept (or) - the same listing API can have both count and set of records, however if table records length is not changing in seconds or minutes - with pagination we will end up querying count db call unnecessarily. Hope this explains 😊

@@SWE-with-VivekBharatha Thanks!

Thank you 😊

Thank you, yeah definitely 😊

Thank you 😊🙌🏻

The example we have shared in context of movies application, where primary entities are movies. As the relation between movies and actors can be many-to-many, we can also have something like this “…/api/v1/actors/:actorId/movies”

This pattern applicability is inside each server (microservice) level where it usually binds to that attached database. Your comment is at architecture level and adding proxy is not useful and adds more latency overall.. Other examples for singleton could be - configuraration class - logger class Let me know if this helps :)

Will push to a repo and add to a pinned comment soon!

Yes, ping is a command, server will return pong if no message is passed else same message will be sent to client

Have you implemented those too in this project?​@@SWE-with-VivekBharatha

​@@AnkitSharma-ml3it I've covered the GET and SET commands, which are among the most frequently used. Once you're comfortable with these, mastering PING will be a breeze! Feel free to contribute to the GitHub repository by opening a PR for the PING command! 😁

@@SWE-with-VivekBharatha okay bhaiya 🔥

Good point, usually once an api end point is production ready, as per the semantic versioning lets say the frequency of major version change would happen once in 5 years as an example and this interval purely depends on the application growth, volume and re-architecture requirements. If an end point in a very short span keep changing then either its not production ready in the first place and we can stick same version until it goes live or bad design in the first place 😉

Yes, absolutely. In context of node, you can configure as reverse proxy and also as load balancer. Just that it has it's limitations to some extent on dynamically spinning new servers and mapping to share the load across with load balancer.

Thanks for your reply I read after I made comment and I understand lot about nginx that it is more than just a webserver it can act as loadbalancer caching and useful in security purpose.

9. Handling Canceled HTTPS Requests...👍

Thank you for the feedback, yes I did at 1.5x 🥲 My bad, realized next day when I watched with fresh context. Now it’s confirmed with your feedback that it’s speed overly adjusted, noted and will be improved from now on 🙌🏻