Really well presented with clarity. Never seen any other video explain this much clearly the defining factors of what a Microservice is. And all the practical key points all through the video are very useful - For instance, deciding the method of communication pattern between Microservices based on the expected response time of the service.

Very clear and concise. Thank you for creating such a helpful video!

I am speechless! god job. you are going to be among the best.

Thanks for sharing your knowleadge with us!

Thanks for great videos and for keeping them to the exact point.

Excellent !!! thank you very much

very great presentation.. down to earth. easy to digest

This is awesome..it's helps me lot.. please post videos like that would help many folks like me...

Thanks for sharing man! Really helped me! God bless!

Good explanation and experience share. Thanks.

Your videos are worth watching, Always waits for your videos, Hope you'll do complete ASP Net Project or Any live session that covers complete ASP NET Core API project.

You have answered my questions in one video thanks bro

Very good video. Thank you.

Hi.. Great video. Eagerly waiting for next part of microservices. If you possible please share the upcoming video topics..

Dude, great content

Great video! It is an informative one and worth watching every minute of your speech.

Hi , its my worth to watch video. very descriptive content amongst all the video I had watched. Thanks for such awesome contents and the way you explained everything. I would be thankful to you if you have any training martial or video from the scratch how to build the microservice and containerized them with the data base and how to deploy them. Thanks Again.

Well made

Great video.

Great video

Thanks for the great content ! I actually had a question, for instance if I have a microservice that needs table A only and another microservice that needs table A and B because of join operations. Does it make sense to keep the 2 microservices or should I just have 1 microservice that will sometimes not use table B ? Thanks :)

Very good video.

Very underrated tutorials, keep up your good work.

Thanks alot to you

Very well explained. Thank you so much for sharing your learning and thoughts. Could you please clarify on the following questions. 1. Can we use containers for heavy traffic sites? 2. If yes, how we can scale out / up containers?

Good explained

One of the main reason moving to Micro Services is the advantage independent scalability. And from my experience end to end testing is much harder with Micro Services and most tend to rely on efficient unit testing within each service.

Can you elaborate on Data Stream? Is it radially available set of tables? Or your custom tables which updates summary information internally? Nice explanation.

Thanks, well explained and crystal! can you share us using Docker and Docker-compose

Is this course still valid in 2022? Do you have any plan to release a dedicated series on Microservice?

Thanks for your awesome channel. please correct the order of videos in your microsevice playlist

Do a serie turning a monolith application with the concepts of microservices.

How Web API is difference than micro services? how can be microservices intergrated with main application?

Could you please cover Abstract factory and Factory Design pattern.

can please put video for micro service with kafka...? and how to document the micro services example swagger

Could you please share slides for this video, that will definitely help.

You mean data stream is like separate report server which will contain data from all micro services. right ? i yes how data is replicated to the report server.

Video is too good

Hi, u video is very useful ! I have a question is if I use efcore orm to create database, how to build migration to generate database with two microservices E.g produce Microservices , order Microservices . what is structure for Microservices modeldata use efcore

See, first, a fall people need to understand is that microservices are not a solution to every problem. Monoliths are still great and there are a number of the application right now in production which is built on it. The services which are now microservices were monolith at some time in the past. One of the biggest hurdles in building microservices is the inter-communication between microservices and maintaining transactions which span across different bounded contexts (different services), once the team found a solution to this problem by adhering to their project requirement, of course, microservices then are easy to build. What I do personally is like I start with a monolith (by keeping separation of concern, but in single solution), once I fill like, now it's time to divide it in a separate solution of simpler microservice, then I tend to start to do it, this way you can learn and it easily separable if you already followed the separation of concern principle while building the same. Then I focus on solving those 2 above major problems. Greate video btw! :) Please make a video on using MassTransit with rabbitmq. That will be very helpful. Edit - I write this comment at 10:00, seems like you are talking the same thing that I wrote here. 😁😁

Tutorial using microservice in dotnet?

Linux SUCKS !!!

Very clear and concise. Thank you for creating such a helpful video!