There are a number of things that are excellent about this video. 1- (Production) Resolution, color, setting, shooting the video 2- (Delivery) Eloquence, knowledge, and clarity of the speaker. High value for 10 minutes. Recommend Highly.
This is the first video I've seen that explains what microservices are without using a lot of buzzwords and acronyms to hide the actual inner-workings of microservices and monolithic api's. Good job!
You can have a ms architecture with as much coupling as a monolithic one, and you can have a monolith with less coupled components than many ms systems have.
I noticed a job application said "breaking down a monolithic application" as experience needed, but they use microservices. Can monolithic be slang for something else? Also can it be partially monolithic and use microservices for other things?
What's the difference between an SOA and a microservices architecture ? We already have a series of services, developed using WCF, (authentication, trading, electronic confirmation etc) for our financial trading platform. does that mean that we already have microservices ? These services were developed back in 2007 when SOA was kind of a buzz word, like is the case of microservices right now.
Disagree on maintenance. That domino effect does not go away with microservices. It just breaks it up. Microservices do depend on each other. You just add the complexity of maintaining multiple apps instead of just one. How much difference is there in load balancing monoliths vs load balancing microservices?
That really depends on the architecture, languages, frameworks, etc. So there's no hard and fast rule with that. For example, if you have an architecture made up of Elixir/Phoenix based applications, it shouldn't matter if it's a microservice or a monolith, since they have the ability to be deployed with no real downtime. But some other languages/frameworks can have downtime during deployment, which can require you to spend more time planning 'maintenance' pages and scheduling updates.
Awesome , This is the first time where i understand exactly what is micro-service architecture it? and what are differences between it and monolithic architecture? Thanks A lot man.
Hi I want to ask you some question is that Can we develop the microservice concept to native application development or not? or This use only for cloud native development? Thank you in advance
I have a question. You mention that a microservice might be, for instance, a frontend that functions as the view for the application, which simply calls the other microservice applications to know what data to render to users. For example, let's imagine a Rails App that serves some data over API and a frontend app written in React/Redux which communicates with the Rails app to fetch/save data into the database. You say that microservices are good because when one microservice breaks down, it does not impact the other part. What if the Rails App goes down? The frontend app wouldn't be able to fetch any data, then. What are the pros and conns of such solutions?
Hey man, I think that some specific microservices are more relevant than others, right? for example if your database breaks down, it'll probably impact many other services. But it doesn't mean necessarily that those other services will also fail. They may keep working, executing other functions that do not depend on the db, maybe... Another situation could be for example if your front-end breaks down. In this scenario many people may think that your entire application is inactive, but it's not true! Other services keep working. In my opinion when he says 'when one microservice breaks down, it does not impact the other part' it means that other parts of your app may keep working, but they must be prepared to handle "connectivity" errors
I worked at a company where the monolithic service was so tightly coupled that aby error caused the entire app to stop working. Monolithic are good but you gotta architect it correctly
It sounds like microservices is a much better architecture style than monolithic. Are there any advantages to monolithic other than faster development time and better (?) performance?
Very well explained. I was facing problem to understand the microservices architecture and most importantly it's advantages and this video explained everything
Excellent and Clean explanation.. I thought of making a video on this topic, but found this video almost similar to my thought process. Thanks for the nice video..
There are a number of things that are excellent about this video. 1- (Production) Resolution, color, setting, shooting the video 2- (Delivery) Eloquence, knowledge, and clarity of the speaker. High value for 10 minutes. Recommend Highly.
This is the first video I've seen that explains what microservices are without using a lot of buzzwords and acronyms to hide the actual inner-workings of microservices and monolithic api's. Good job!
Those first 5 minutes really helped me get the difference. Best quick intro, and I have watched 5 similar today.
You can have a ms architecture with as much coupling as a monolithic one, and you can have a monolith with less coupled components than many ms systems have.
thanks , those are a truly key features as well as you can also scale parts of application separately as well
Very clear, Thanks a lot! Never wasted a second watching this.
A perfect explanation coupled with a class recording setup.. Awesome dude...
Glad you liked it!
I noticed a job application said "breaking down a monolithic application" as experience needed, but they use microservices. Can monolithic be slang for something else? Also can it be partially monolithic and use microservices for other things?
What's the difference between an SOA and a microservices architecture ? We already have a series of services, developed using WCF, (authentication, trading, electronic confirmation etc) for our financial trading platform. does that mean that we already have microservices ? These services were developed back in 2007 when SOA was kind of a buzz word, like is the case of microservices right now.
Good crash course, but I wanted a little why microservices is not just SOA
Disagree on maintenance. That domino effect does not go away with microservices. It just breaks it up. Microservices do depend on each other. You just add the complexity of maintaining multiple apps instead of just one. How much difference is there in load balancing monoliths vs load balancing microservices?
That really depends on the architecture, languages, frameworks, etc. So there's no hard and fast rule with that. For example, if you have an architecture made up of Elixir/Phoenix based applications, it shouldn't matter if it's a microservice or a monolith, since they have the ability to be deployed with no real downtime. But some other languages/frameworks can have downtime during deployment, which can require you to spend more time planning 'maintenance' pages and scheduling updates.
Very simple and clear explanation without overcomplicating things. Thanks!
I'm glad that you found it helpful!
Awesome , This is the first time where i understand exactly what is micro-service architecture it? and what are differences between it and monolithic architecture?
Thanks A lot man.
I'm glad that you found it helpful!
Thank you. I enjoyed how you explained the difference between the two.
Hi I want to ask you some question is that Can we develop the microservice concept to native application development or not? or This use only for cloud native development? Thank you in advance
Really great explanation. The best I've seen so far. Thanks!
Exactly the explanation I was looking for in a simple way. Thanks Jordan :)
I'm glad that you found it helpful!
I have a question. You mention that a microservice might be, for instance, a frontend that functions as the view for the application, which simply calls the other microservice applications to know what data to render to users. For example, let's imagine a Rails App that serves some data over API and a frontend app written in React/Redux which communicates with the Rails app to fetch/save data into the database. You say that microservices are good because when one microservice breaks down, it does not impact the other part. What if the Rails App goes down? The frontend app wouldn't be able to fetch any data, then. What are the pros and conns of such solutions?
Hey man, I think that some specific microservices are more relevant than others, right? for example if your database breaks down, it'll probably impact many other services. But it doesn't mean necessarily that those other services will also fail. They may keep working, executing other functions that do not depend on the db, maybe...
Another situation could be for example if your front-end breaks down. In this scenario many people may think that your entire application is inactive, but it's not true! Other services keep working.
In my opinion when he says 'when one microservice breaks down, it does not impact the other part' it means that other parts of your app may keep working, but they must be prepared to handle "connectivity" errors
Each microservice will have its own ui, logic, and data.
Isn't this just the single responsibility principle? Or APIs under a different name? Could you do this in PHP using "public static" everything?
THANK YOU for posting this. Awesome stuff. Stay safe & healthy.
Thanks! You too
When you say timeline and budget . Do you believe MS can be stretching vs Monolith?
honestly microservice at the start will strectch budget compered to monoliths but later microservices will save lots of money
I worked at a company where the monolithic service was so tightly coupled that aby error caused the entire app to stop working. Monolithic are good but you gotta architect it correctly
Micro services alone won't avoid tight coupling between modules.
It sounds like microservices is a much better architecture style than monolithic. Are there any advantages to monolithic other than faster development time and better (?) performance?
Those are the key items. The simplicity of the build also leads to a smaller learning curve.
Very well explained. I was facing problem to understand the microservices architecture and most importantly it's advantages and this video explained everything
I'm glad that you found it helpful!
Very nice video. Clear and straightfoward. No bullshit added just to sound intelligent. Good work.
I'm glad that you found it helpful!
wait, does this also apply to operating systems? monolith vs microkernel? Amazing delivery btw, thanks.
nah, not really. similar but microkernel/monolith kernel refers to where services are run - user space or kernel space.
very well explained. thanks for sharing!
Thank you guys for this reeeeally useful explanation! Subscribing this channel right now!!
I'm glad that you found it helpful!
Nice intro to the topic.
Excellent and Clean explanation.. I thought of making a video on this topic, but found this video almost similar to my thought process. Thanks for the nice video..
Glad it was helpful!
Very well explained.Thanks
Very good explanation, thanks
One of the best and simpliest explanations :)
Thanks!
Awesom vid. Finally got the definition of microservices smashed and delivered on a silver plate.
I'm glad that you found it helpful!
Many thanks to you. Great explanation
I'm glad that you found it helpful!
Great explanation! Thanks!
I'd like to thank you for this video. Helped a lot. Really recommend.
I'm glad that you found it helpful!
Perfect explanation. Thank you
Amazing explanation. Thank you so much.
This is great man.
Very useful explanation ... Thank you
Very clear explanation..
Great explanation!
Thanks!
Very good information to a newbie
I'm glad you enjoyed it!
Thanks alot for this great explanation
Micro fad.This architecture was used way before it even had a name. However, this is a good presentation on the topic. Thank You
Lots of thanks to you..
Thank you so much
You're welcome!
Great Video....Loved it
I'm glad that you enjoyed it!
Thanks
Good stuff.thanks
You're welcome!
A debate should have winner...
Not upto you 😜
Great!
thanks, this explanation is very made sense
big ups big dawg
monolithic easy to corrupt, funny that
First of all, it's a great explanation, thank you so much,
But bro, that's not how we hold a marker
Thank you so much
You're most welcome!