I watched this video from a browser I wasn't signed in, had to change to a signed in browser to say "Thanks so much for the video". Precise and concise
Microservices didn't appear because they needed to tackle complexity. In fact, Microservices takes complexity up to a whole new level. The main reason for Microservices to appear is tackling scaling issues (of both number of users and the teams that builds the software) and tight coupling issues between the different components (or tiers) of a system that makes evolving the software much harder and much slower than what was needed. I felt you make this case in the beginning but kind of save it in the end. But a good video overall.
we literally swtiched to Rust and now we are a monolith. We cut off the unneccessary complexity caused by our microservcies by using Rust which can millions of concurrent io calls per second...
The question is when to use it...people who in last years have used cause "fashion/hype" are regretting, once again... "hype oriented", worst thing in software development and seems to have no end...
@@gt4adolfo I dont know your app requirements but that is the exact type of thing we want to avoid, the level of scale you need to hit before MS starts making sense from a performance/cost/technical debt side of things is what most companies will never experience. We literally just rent a 8 core server on aws and thats that - it handles 500k MAU just fine. Even StackOverflow is built on a monolith... and I'm sure they see more scale than we ever will... You will never see "oh 1M users were added overnight and our servers crashed since we werent able to handle the load" scenarios.
It is a bit shocking to see that you seem to be the absolute minority in this comment section, but at least the amount of upvotes give me some hope. The last companies I've worked for started implementing microservices because they thought it would fix their issues (mainly with complexity) and it made it worse in every case. This video also gives the impression that creating a monolith is the "old" way of writing software and microservices are the modern solution to all of our problems and this seems to be what most people are thinking. The reality is, that most companies are neither Google nor Amazon and switching to microservices just introduces a great lot of new problems for them. There are companies with internal software that is far off from being anything complex (you can run that on a raspberry pie without mayor issues) and used by less than a 100 employees where they switch to cloud-based microservice architectures because apparently this is what has to be done right now. Of course they do also have only a few developers which now have to handle not just one system, but a dozen services instead. I've not yet seen this having a positive impact anywhere. But I've seen it having a very bad impact a lot of times. There are single teams with 5 devs having to manage 20+ services out there.... And the worst part of that is, that they don't even manage to leverage the positive aspects of microservices. Most of the implementations I've seen are neither scalable (for example all using the same bottleneck database), nor independent (like all referencing the same model library). I don't think the technology itself is bad, just that it seems to be misused most of the time. I'd argue that the best way is to build a monolith first (using proper architecture!) and if you see that you for example run into performance issues because of a specific part of that application and you can provide the devs to tackle this, you extract that part into a microservice and build that one to be as resiliant and scalable as possible. But what do I know, the managers apparently know it better ¯\_(ツ)_/¯
Simple, straight to the point, no meaningless animations, no meaningless stuff to look "cute" (the ones who are doing it trust me it's very annoying). Very well explained, please keep it that way.
Fantastic breakdown! Your concise explanation in just 5 minutes is a game-changer for anyone diving into this complex topic. Clear, insightful, and incredibly helpful. Kudos!
Thanks for the idea. However I don't plan to dig into implementation and programming at the moment. The purpose of this channel is to introduce software and architecture concepts in easy to understand 5 mn videos.
each concept have their advantages and disadvantages.. I have experience with both Monolithic & Microservices.. I prefer microservices because of below reasons 1. Scaling of required functionality 2. Easy to understand the code 3. new comers can start contributing within a short period 4. Easy to debug the issues for new comers
Ohh my gawdddd, it is after wtaching such videos of urs, experiencing learning in such an awesome way through ez smooth af animations, content & explanation. This makes me realize that technology is evolving everyday and we're living in a tech era. Nice work
whats the difference between a bunch of microservices working in tandem under a single software application, and the traditional monolith system that also had various processes working in tandem under a single software application? As someone who does not know anything about this topic, my takeaway was that microservice architecture uses network protocols and the software is distributed over a network as opposed to monoliths where the entire software package existed on a single host. Is this correct?
Your understanding is correct. Actually an app designed as microservices would usually be less performant because of the added latency of network communication between microservices... The main reason why someone would like to design an app as microservices is decoupling. Decoupling when done right increases agility (how fast you can release new features), maintainability, and most importantly scalability.
@@5-minutesorless Thanks, this makes a lot of sense and I am amazed I learnt all this in less than 10 minutes. I liked your video and subbed your channel, but was shocked to see this was your first and only upload. The quality is great, keep it up.
Microservices only re-arrange components, which may help to reduce IT-complexity to some extent. However, microservices don't do anything to address complexity in IT-systems driven by underlying complexity in business processes and business rules. If nothing is done about (needless?) complexity in business processes of an organization, devising IT-solutions to handle that complexity will always be something like fighting running battles at best.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
I watched this video from a browser I wasn't signed in, had to change to a signed in browser to say "Thanks so much for the video". Precise and concise
Thank you for watching and the nice comment 🙏
Clicked on this expecting to learn one thing….and learned 20. The best 5 minute investment of my time I’ve made on RUclips in months.
Microservices didn't appear because they needed to tackle complexity. In fact, Microservices takes complexity up to a whole new level. The main reason for Microservices to appear is tackling scaling issues (of both number of users and the teams that builds the software) and tight coupling issues between the different components (or tiers) of a system that makes evolving the software much harder and much slower than what was needed. I felt you make this case in the beginning but kind of save it in the end. But a good video overall.
we literally swtiched to Rust and now we are a monolith. We cut off the unneccessary complexity caused by our microservcies by using Rust which can millions of concurrent io calls per second...
@@perc-ai thats true we have a monolith wrote in rust, but we are moving to a MS architecture using rust and go... it's easy to mantain and scale
The question is when to use it...people who in last years have used cause "fashion/hype" are regretting, once again... "hype oriented", worst thing in software development and seems to have no end...
@@gt4adolfo I dont know your app requirements but that is the exact type of thing we want to avoid, the level of scale you need to hit before MS starts making sense from a performance/cost/technical debt side of things is what most companies will never experience. We literally just rent a 8 core server on aws and thats that - it handles 500k MAU just fine. Even StackOverflow is built on a monolith... and I'm sure they see more scale than we ever will... You will never see "oh 1M users were added overnight and our servers crashed since we werent able to handle the load" scenarios.
It is a bit shocking to see that you seem to be the absolute minority in this comment section, but at least the amount of upvotes give me some hope.
The last companies I've worked for started implementing microservices because they thought it would fix their issues (mainly with complexity) and it made it worse in every case.
This video also gives the impression that creating a monolith is the "old" way of writing software and microservices are the modern solution to all of our problems and this seems to be what most people are thinking.
The reality is, that most companies are neither Google nor Amazon and switching to microservices just introduces a great lot of new problems for them.
There are companies with internal software that is far off from being anything complex (you can run that on a raspberry pie without mayor issues) and used by less than a 100 employees where they switch to cloud-based microservice architectures because apparently this is what has to be done right now. Of course they do also have only a few developers which now have to handle not just one system, but a dozen services instead.
I've not yet seen this having a positive impact anywhere.
But I've seen it having a very bad impact a lot of times.
There are single teams with 5 devs having to manage 20+ services out there....
And the worst part of that is, that they don't even manage to leverage the positive aspects of microservices. Most of the implementations I've seen are neither scalable (for example all using the same bottleneck database), nor independent (like all referencing the same model library).
I don't think the technology itself is bad, just that it seems to be misused most of the time. I'd argue that the best way is to build a monolith first (using proper architecture!) and if you see that you for example run into performance issues because of a specific part of that application and you can provide the devs to tackle this, you extract that part into a microservice and build that one to be as resiliant and scalable as possible. But what do I know, the managers apparently know it better ¯\_(ツ)_/¯
This is how I learn every topic. Now I see someone who doing the same thing. Appreciate it. This is the way of teaching something.
Simple, straight to the point, no meaningless animations, no meaningless stuff to look "cute" (the ones who are doing it trust me it's very annoying). Very well explained, please keep it that way.
Thank you for the feedback, much appreciated 👍
Well said ❤
Fantastic breakdown! Your concise explanation in just 5 minutes is a game-changer for anyone diving into this complex topic. Clear, insightful, and incredibly helpful. Kudos!
Wow i must say
I was confused about micro services
But now you cleared my doubt about micro services
Thanks a lot
Happy to help
Hands down the best microservices introduction ever.
thanks 🙏
This is a well animated and presented introduction to the microservice paradigm. Good job!
Thank you for watching!
Since i recently work with microservoce, this video is really helpful to me 💯
Glad it was helpful ☺️ thanks for watching 👍
Bestest among the best.. Thank you sir
Mark my words, this channel is going to blow up!
🤯 thanks
simple, clear, straight explanation, thank you
you're welcome, glad you appreciated
Very clean and easy to understand, thanks for the video
Thank you!
Really clear presentation. Great job 👍
Never seen such an explanation on Micro services.. subscribed
Thank you
This is best video with all details in 5 min.
Thank you 🙏
Absolutely excellent explanation. Thank you.
Glad it was helpful!
This is very useful for beginners who want to understand introduction to Microservices. Thanks and great work !
Glad you think so! 😊
Thanks this was way easier to understand than other resources. Other videos only confused me further, yours is concise and precise.
hey man, this is really good! You should keep doing videos like these, explaining complex topics in simple to understand 5-minute digestible videos.
Thank you. Yes, more is coming. It just takes some time to create such videos.
Except this wasn't 5 minutes.
So far, this is the best video which provides easy to understand and concise info. Thanks for creating this video!
This is an excellent summary. Would love to see similar videos on containerization, orchestration, etc!
The first ever video of this channel now has 55K views, and was uploaded 11d ago? Man, gotta suscribe!
thanks for watching and subscribing 🙏
Clear and crisp info about microservices ,good job.
thanks for watching
@@5-minutesorless Would you be coming up with implementation of Microservices with NodeJs/Spring Boot?
Thanks for the idea. However I don't plan to dig into implementation and programming at the moment. The purpose of this channel is to introduce software and architecture concepts in easy to understand 5 mn videos.
The best explain on all RUclips thanks
thank you for watching 👍
from the way you teach a thoery,i judge that you are a genius
Amazing! To the point, no fluff. You understand the concepts in 5 minutes!❤
Ah....Sometimes an explanation can be sooo elegant eh?!
Almost like poetry...😊👍
Thank you so much! 🙏
your content is amazing ,please upload more viodes.
I love this channel just by its name. And I'm sure I'll love it even more after finishing this video!
thank you 🙏
Next level presentation skills...Fabulous Thanks ❤
So nice of you
I'm guessing Rest APIs and JSON is used for i/o and cross comms between 'microservices'
correct
out standing animated and well explained, which tool you use ?
Thanks. Power Point and Davinci Resolve for editing.
Nice start, keep adding videos. Thanks
Thank you, I will
brilliant presentation. Concise and to-the-point.
thanks 🙏
Awesome video man! Where are the rest of the videos. Keem em coming! 🤔🤯
Thanks 🙏
You were given valuable information thanks 👍😊
Glad it was helpful!
Very well explained Sir. Just Keep it going please....!!!
Thank you
Excellent Video. Very clear, conscise and made perfect sense. Great job.
Very clear and articulate explanation.
Glad you think so!
Hi, Keep doing & explain more topics you are explain simple & Easy to understand method. I appreciate your work. Good Job. keep doing.
Thank you!
very nicely explained, this is the first video i understood
Awsome. Thank you for watching.
Great, thank you.Very informative
Waiting for your next video
So nice of you
Excellent Explanation. Thank you very much for the knowledge sharing... 🙏
My pleasure
Useful. Thank you.
Glad it was helpful!
That's the best way to explain microservices. Thanks man
thank you 🙏
each concept have their advantages and disadvantages.. I have experience with both Monolithic & Microservices.. I prefer microservices because of below reasons
1. Scaling of required functionality
2. Easy to understand the code
3. new comers can start contributing within a short period
4. Easy to debug the issues for new comers
these are very valid points.
Wow crystal clear. I will share this video to my team 😃
Awesome, thank you!
Many thanks for good Explanation.
thank you for watching 👍
Thanks for sharing such a useful video
So nice of you
Love this video please make more related to Cloud technologu
I am still new to microservices, and the first thing that troubles me was how to handle database transactions across all the microservices.
thanks for the awesome video.
please keep uploading.
Very well explained with appropriate animations👍👍
Glad you liked it
You really explained it so well in a short time frame 👏
Thanks a lot 😊
Woah.. Fantastic explanation. Please do more
thank you.
need more clear explanation like this.
sure. Thanks
Ohh my gawdddd, it is after wtaching such videos of urs, experiencing learning in such an awesome way through ez smooth af animations, content & explanation. This makes me realize that technology is evolving everyday and we're living in a tech era. Nice work
Thank you so much 😀
Well done. Short and sweet!
Thanks
Great explanation and good use of graphics which must have taken you quite a time to create. Thank you
Very nice explanation keep up the good work
Thank you for watching.
thank you! I was looking for a concise video like this
Is the MVC pattern multitier? Seems to fit the 2nd example.
Yes, it does.
Please add more such short and informative videos
I will. Thanks!
Very nicely explained. Amazing graphics.
Best explained video on Microservices .. keep making such high quality videos bro 😀☺
Definitely Subscribed 😊
Thanks a ton 🙏
whats the difference between a bunch of microservices working in tandem under a single software application,
and the traditional monolith system that also had various processes working in tandem under a single software application?
As someone who does not know anything about this topic, my takeaway was that microservice architecture uses network protocols and the software is distributed over a network
as opposed to monoliths where the entire software package existed on a single host.
Is this correct?
Your understanding is correct. Actually an app designed as microservices would usually be less performant because of the added latency of network communication between microservices...
The main reason why someone would like to design an app as microservices is decoupling. Decoupling when done right increases agility (how fast you can release new features), maintainability, and most importantly scalability.
@@5-minutesorless Thanks, this makes a lot of sense and I am amazed I learnt all this in less than 10 minutes. I liked your video and subbed your channel, but was shocked to see this was your first and only upload. The quality is great, keep it up.
Really nice animation! Great video! Any chance you'll do a video on scaling distributed systems?
Thanks. Yes, possibly, I was thinking about creating a video about explaining high availability concept that would include scalability.. stay tuned 😉
wow very nice idea , explain everything in 5 minuts
Thanks for watching!
great explanation. wonderful.
Thank you!
You will reach 1000 subscribers in no time, keep doing these please
👍
It was great. It gave me some clues about microservices and tools associated with them. Thank you!
Glad it was helpful!
Good job, well done.....nice keep it up..
Thanks a lot
Thanks! What a great explanation
great and straight to the point video, thanks!
a very intuitive video, congratulations!!
Thank you! 😃
Awesome explanation by putting the architecture in historical perspective!
Glad you liked it!
Thanks for clearing my doubts in the 5-minute video😍
Great explain 👍👍👍 Keep it up
Thanks 🙂
Very well explained and illustrated
Thanks for watching
These qualities videos will surely bring a revolution in tech tutorials especially on RUclips. 🔥 Thanks and waiting for more content.
Thank you for the nice comment!
Thanks for this content. It is very helpful.
Glad it was helpful! Thanks 🙏
How did you do that animation at 2:25 ?
PowerPoint. The Morph transition.
really enjoyed watching the video
Thank you 🙏
so it essentially is closer to having multiple api endpoints, each tackling a different logic right?
Cool video!
Which tool did you use to create such amazing animation?
Powerpoint and DaVinci Resolve for video editing
Amazing video. Learnt alot. Keep up the good work. Would love more videos like this.
I am your 79th subscriber, do release more videos
Thank you for watching and subscribing. Yes, sure, more is on the way 😉
Amazingly explained subbed
Awesome, thank you!
Great Video, Well Explained.
Glad you liked it
Nice presentation, thanks
Glad you liked it!
You guys did an awesome job here.
thank you 🙏
mate, you are legend! this video is precisely what I was looking for, thanks
Thank you! Glad it helped 🙂
Good video and also a fair comparison between the microservice one and the monolithic one
thanks 🙏
Great video. Could you please tell, which tool you use for these beautiful animations in the videos?
Thanks.
thanks. PowerPoint and DaVinci Resolve 😉
Great video, thanks
Super uself and concise explanation. Thanks!
thank you 🙏
Microservices only re-arrange components, which may help to reduce IT-complexity to some extent. However, microservices don't do anything to address complexity in IT-systems driven by underlying complexity in business processes and business rules. If nothing is done about (needless?) complexity in business processes of an organization, devising IT-solutions to handle that complexity will always be something like fighting running battles at best.
I agree completely 👍
Very Informative. Thank you.
Thanks 🙏