How to build a Nodejs Microservices RPC in 25 Minutes

Nodejs Microservice tutorial, Through this video we will learn how to communicate with other microservices through RPC calls and split the read and write responsibilities.

It is highly recommended to code with me if you are comfortable so you can move your progress step by step.

Previous Episodes:

You can find the source code from the link below to compare your code.

Microservice source code:

My little contribution help you to grow I will be pleased.

Thank you.

#microservices #nodejsmicroservices #nodemicroservice #nodejstutorial #Microservice #nodejsbiginner #nodebackend #js #nodetypescript #typescript #es6 #nodejsapi #microserviceCommunication

[vungocduyet]

So glad you're back! (I'm Vietnamese)

[moutazsh]

Thank you very much it was a great tutorial series and looking forward for the next episode, would be great if you can publish it soon so we can continue watching with a fresh brain. :)

[bamii_a]

enjoyed every bit of knowledge shared throughout this series 💯

[tranquillityEnthusiast]

Great, looking for more concepts under microservices.

[pbdivyesh]

This series has helped me understand way better than anything else out there. I've created a plan to teach myself better backend and cloud level programming to advance in my career. So my plan was to follow Designing Distributed Systems book and some video on youtube. You have kept it really ideal in terms of indexing the concepts and explaining. Thank you so much for all these work. In the book I'm at 4th Chapter Adapter(s) just before Serving Patterns, and these videos have helped me imagine them in a articulate manner.

[pratyakshgupta]

One of the best content on complete implementation of microservices. If you can provide the link for these architecture diagrams it will be a great help. Love your content

[saeedahmadian]

Thanks for your awesome content, I really learned a lot from you.
There is only one issue when you create queue with name as empty string to receive data from another service, in this case every time you run this line of code Rabbit MQ manager will create a queue with specific name ( although you just see empty string and think there would be only one queue but if you check the manager you see pile of queues generated with each request). Isn’t it better if you specify a name father than empty string? You only need to release consumer whenever you receive the message from another service.

[engineerbarkat]

Hi, Jay thanks for this video. Great learning so far, I have watched this series and created a project like a social media application where I have created 6 services and created 6 different DB for each service, I am following the CQRS design pattern.

1. posts service => to store posts details,
2. users service => to store user's details,
3. comments service => to store comments details,
4. applauds service => to store applauds details,
5. shares service => to store shares details,
6. query service => to store all the details in a single DB but separate tables to query the data together,

But I found some problems if we need some post information while commenting on the comments service. Like we have a feature called disabled Interaction => if the user disabled the interaction while creating the post another user can not make comments on that post to achieve this feature we need to post details while creating comments I think now I can implement that feature using RPC in our project.

AGAIN !! BIG THANKS FOR CREATING THIS SERIES, IT HELP ME TO LEARN THE MICROSERVICE CONCEPTS I AM WAITING FOR UPCOMING VIDEOS ON THIS SERIES.🤟🤟💌

[faisalplusplus]

Hi Jay, thanks for this super useful video series. My question is if we use multiple micro-services then their internal communication will add huge latency. How we can handle it?

[moutazsh]

Why do we have channel.consume on RPCObserver and request data, shouldn't we only be able to consume the message on the listener not reciever ? Sorry, I have a lot of question but I'm totally confused. Do you have any documentation that can help me to start with ?

[moutazsh]

Hi, hope you are doing well.
I truly couldn't understand how they get data from each other, so for example If i hit custmer/wishlist api end point.
then a new rpc will be triggered RPCRequest("PRODUCT_RPC", requestPayload),
after that the requestData will send new stuff to the queue, what happen then. How do we get the response from product service while we call the customer service. is the RPCObserver triggered or what ?

[amanullahghouri]

i think now you should to make an professional level series on microservices do you have any paid tuts series for microservices,
thanks you v much

[tilter]

Hello, I really enjoyed this series and followed along with you step by step. However, there's a part I didn't quite understand, which is why we implemented the RPC part. As far as I can tell, we canceled the publish and subscribe for some services and implemented RPC instead. But from what I've seen, the pub/sub process also works similarly to RPC, facilitating data transmission between services. I couldn't grasp the main differences despite watching those parts of the video multiple times. Could you please explain briefly?

[NathanielBabalola]

Jay you're back, where have you been?
I messaged you on Skype too

[PrashantShekher]

Can Kafka, SQS, NATS, etc. be used to implement Node.js microservices with RPC?

[amirzahran]

Is this the last episode of the course?

[skyax]

Love the videos but I wish you didnt move so fast it was hard for me to follow all of that because i am new to miroservices. Thanks

[moutazsh]

I don't get it why not to just publish to the channel and the subscribers will do the exact actions, instead of calling requestData and that will call the publish to the queue ?