Microservices Architectural Pattern 

Enjoy the video and please let me know if you find the video a little bit too long so that I can split it into two parts. ^^

You are really good at explaining these things. I'm super impressed and grateful to run into this video.

All your lectures are neatly organized, very informative.

The concepts on the video were very clear, now i have good basic understanding of how microservices, and microservice architectural pattern work. Keep up the good work.

You saved me from having to buy another course on Udemy. I also have been keeping a running list of the resources your recommending. Thanks!

Best explanation out there! Thanks a lot I learned a lot and I really enjoyed further reading part at the end. Keep up the great work!

You look like you have a great RU-vid channel. Great voice, pace, good use of English language, and graphics. However you don’t have any recent postings. That’s a killer.

Very crisp, informative video. Thank you.

Hey mate...You're amazing....Would you, please, make some vids about the Design Phase of the SDLC and the different approaches of designing a software...There are no great resource about it out there in youtube...Thanks.

Interesting way to think as a bitter alternative to layered system :)

You mentioned microservices testing as a pro. But that's one of their biggest cons, they are extremely hard to test when compared to other architectures.

Great introduction to Microservices. Thanks a lot for putting it in..:)

Hello, you have the best videos on the topic. Can you please make one about async, coroutines and stuff? It's a new trend, I'd like to know proper theory behind it and I assure you many others would like to learn it too. I hope it's not out of your area of expertise.

That was a nice and short explanation, OK!

awesome stuff...great Job

Timeout in a Microservices world is an "antipattern" because of the dynamic nature of the pattern. Better way is to use patterns like circuit-breaker or rate-limiter to handle high traffic or responsive client.

Bravo!! Thanks for this.

Thx for explaining. You sound like Jay Baruchel :"D

Thanks for presenting things neat. :)

Awesome video !

Sharing DB between microservices is always a bad idea. If you want to have something that is middle ground then always choose modular monolith and when ready go to microservices but always with separate DBs.

@Techcave where do you work brother? Your knowledge is on point. How much experience do you have?

1) can microservice architecture be used in TCP socket based client server application 2) can the TCP server also create API similar to rest HTTP My second question might be bit confusing ,so I am , please help me understand

Enjoy the video. but the cons of the microservices seems to be indigestible. The whole purpose of MS is to decrease latency and increase response time and negligible down time. So, how cud u say that latency increases? How transaction is difficult? I am new to all these things so may be not able to relate. Please explain if you could.

wonderfull !!!

is the voice generated by computer? Without criticizing

please tell me how to connect docker in .net c#

For most of projects, my experience is "don't use microservice"

So sad seeing you go

Android phones

Good content but the quality of the speech is awful. Monotonic, jittery and full of English grammar hiccups