Видео

@@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.

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 🙌🏻

Good question! Simplifying API naming conventions boosts consistency and developer productivity, but security wouldn't be compromised. Security is a separate layer that must be strictly enforced like authentication, authorization, rate limiting, and data validation are crucial to protect APIs from risks - irrespective of how simple or complex the naming conventions are. In summary, even with self-explanatory naming conventions I don't see of a case where it exposes any security risks. If you can share an example, I can definitely explain in accordance with it. Thanks for dropping a comment - appreciate the thoughtful question! 😊

Thank you 🤩

Thank you 🙌🏻

Thank you very much! Hope you enjoy the course 😊

Hi thanks for your interest. There will be 2 more videos on persistence modes - Snapshot and AOF (Append Only File) And last video will share a roadmap on extending and adding other data structures support. I am planning to complete by next weekend 😄