I’m willing to bet in a few years the industry will refer to “micro services” as a Thousand Islands and “monoliths” will turn into Panacea. Then tell us how coding in one style in a common code base with a single installation is so much better, reducing the maintenance nightmare, inter-system integration problems, and sub-fiefdoms that arose from the Thousand Island approach.
This must be the only video explaining the whole concept in comparison so clear. Really brilliant as always from IBM Cloud. You should create an academy. But, you might not need microservices. Do not get dazzled by the buzz around microservices and spend months trying to convert your monolith to microservice architecture. Dell's example on how they screwed 18 months of work with 120 developers just to convert their application monolith to microservices must be a good example on much & many things can & will go wrong. The only thing I would suggest double-checking before making the decision of microservices is language independence. In real-world applications that's not something to be taken for granted.
what about fetching data from different services. would it be painful if those has separate databases. how it would effect the time to fetch and coordinate those informations?
@@IBMTechnology I asked my group of IT professionals to watch the video for listening practice and vocabulary acquisition. They're all involved with apis and microservices at work. Then in class I highlighted some of the phrases you use in the video. off the bat under duress up and running talk over APIs thereby at best And we all created examples and conversations based on those phrases The idea behind this is to expose them to good sources of spoken English with themes familiar to them. So thank you very much, they all liked the class and your video. And the way you use that glass to write on makes the watching experience really interesting.
I was wondering the same. They flip the video, so most of the guys become left-handers :) Explained here: th-cam.com/users/postUgzf5SL_yh9NglCJzgF4AaABCQ
So if all the microservices could be written in their own language. How do the communicate? Do they usually send strings, json or some other protocol? Because remote method invocation would be difficult if they use different languages.
Through network using protocols such as HTTP or even lower-level such as TCP or UDP. Sometimes you go higher level and use GRPC wich uses HTTP2+ under the hood.
Kind of odd that when I tried to watch this video as embedded in IBM's own microservices article I get the error, "Unauthorized domain: We're sorry, this content is only available on certain domains."
Thanks a lot for this! Though I would like to ask, what is a DevOps pipeline? Any examples, please. Is it like a testing software? Please elaborate. Thank you.
Push code to branch in GH -> build that code (jenkins job start) -> test it -> deploy it (optionally, end of jenkins job) there is one Pipeline example.
Hey, there! In short... yes! 🙂 Infrastructure as code (IAC) allows for consistent automated deployment of infrastructure which decreases manual errors and increases efficiency. We have quite a few resources, too, if you'd like to explore more on this subject: 🎦 What is Infrastructure as Code (video): ibm.co/2OioRC5 ▶️ Tutorial: ibm.co/3p09RoY ➡️ Article: ibm.co/3rDrQDz
If you are a start up or even developing something in a company that hasn’t been validated should you really go ahead and build a micro service based architecture considering it’s more timely and expensive? I’d rather build something quick and dirty and get it out to my customers and get feedback than spend time building a complex architecture that might not be relevant because our customers don’t want what we’re building. Does anybody have an opinion on this?
I think the real world no real decoupling things. New business requirement come always caused changing from top to down, so here, it could be change required in thousand islands...
Nice try but no. The explanation is good but the benefits of the microservices architecture are not realistic - having multiple langs to deal with and maintain is a nightmare, infinite contracts and apis - instead of writing logics you write all that stuff (same bullshit as writing unit tests which create a false sense of everyting is ok). Most of the time microservices are not reusable. If a microservice is down youd probably want all your app to be down, because it creates a false sense that the app is running normaly which is not. There are other drawbacks which I dont want to describe as it becomes too long. The best approach is having a monolith (with heavy coupled logics) and few critical/exposed standalone and reusable services, which run long-running tasks.
This presentation is sadly very superficial. For any IT system, there are many different ways to allocate functionality to deployable units - ie there is a sliding scale from one company-wide monolith to a handful of larger systems to many smaller systems to truly function-level components. Each different level of granularity has its own advantages and disadvantages, and the optimal solution is likely to differ by business area - ie the optimal solution for a large system can well be a mix of components of different granularity. Very few large companies have a single monolith, and I doubt many companies use 100% fine-grained services either. Fine-grained components have some important advantages, but also some very nasty disadvantages. Moderate-grained components can potentially support elastic scaling without needing to be "single functions". What is presented here are truly two extremes, and while the disadvantages of huge monoliths are presented, the (many) problems with truly fine-grained systems are not discussed at all.
"Every app function is it's own service"
That's the line I needed to see. Now I get it.
Thank you.
Great example of how to deliver a complex topic in an easily understandable manner - thanks
AMAZING explanation, captures really important details in a simple way. Thank you.
Thank you for watching, we're glad you found it useful! 👍
Thank for explaining in such an easy manner.
4:30 "A distributed monolith", awesome!
I like the way he summarized this very intensive task at 2:58
I’m willing to bet in a few years the industry will refer to “micro services” as a Thousand Islands and “monoliths” will turn into Panacea. Then tell us how coding in one style in a common code base with a single installation is so much better, reducing the maintenance nightmare, inter-system integration problems, and sub-fiefdoms that arose from the Thousand Island approach.
Totally agree. And they'll be making videos just like this one to sell us on it.
It depends honestly. if you are a 10 person team with a straightforward application, the microservice overhead might not be even worth it.
@@sinajafarzadeh9577 can u please guide me more about integration process management (ipm). i am a fresher in an IT company and got this as my domain
And repeat this over and over in the next decades lol
Uff! Couldn't agree more
This must be the only video explaining the whole concept in comparison so clear. Really brilliant as always from IBM Cloud. You should create an academy.
But, you might not need microservices. Do not get dazzled by the buzz around microservices and spend months trying to convert your monolith to microservice architecture.
Dell's example on how they screwed 18 months of work with 120 developers just to convert their application monolith to microservices must be a good example on much & many things can & will go wrong.
The only thing I would suggest double-checking before making the decision of microservices is language independence. In real-world applications that's not something to be taken for granted.
Brilliant video. Thanks Dan!
Nice job, Dan. Good seeing you again!
Great Lecture that wasnt a boring lecture!!!
Loved your explanation!!
Very clear and easy to understand! Thanks for the great presentation!
Thank you for watching! 🙌
Simple, interesting and example-based explanation. Thanks!
Very clear and helpful explanation. Just the right pace and amount of information.
OMG best explaination ever!
Very helpful video! Also this reminded me how much I love lightboards
Thanks for making these concepts so easy to understand.
clear explanation of complex concept in understandable manner
Thanks for the video ! Very Helpful 🤟
what about fetching data from different services. would it be painful if those has separate databases. how it would effect the time to fetch and coordinate those informations?
so bright and clear explanation !
What a fanstastic, smart presentation!
Very straight forward and easy to follow. Great video.
Best video on microservices
Thank you! 🙏
Thank you , I'm gonna use this video in an English class.
Hi Teacher Chil...please let us know how that goes! Thank you for watching.
@@IBMTechnology I asked my group of IT professionals to watch the video for listening practice and vocabulary acquisition. They're all involved with apis and microservices at work.
Then in class I highlighted some of the phrases you use in the video.
off the bat
under duress
up and running
talk over APIs
thereby
at best
And we all created examples and conversations based on those phrases
The idea behind this is to expose them to good sources of spoken English with themes familiar to them.
So thank you very much, they all liked the class and your video.
And the way you use that glass to write on makes the watching experience really interesting.
Amazing explanation best one I’ve seen so far
Simply explained, thank you..
This concept blew my mind!!
Brilliantly & simply illustrated. Especially from a technical and architectural vocabulary.
Marc we love to hear this! Thanks for visiting our channel. -Dan
Amazing explanation and wondaful elaboration. Thank you.
Awesome explanation - Thank you
Very awesome video with perfect notes. thanks...
Finally, I understand. Thank you. Btw, are you really writing backwards or you just sort of flipped the video?
I was wondering the same. They flip the video, so most of the guys become left-handers :)
Explained here: th-cam.com/users/postUgzf5SL_yh9NglCJzgF4AaABCQ
great video, thanks 😊
Thanks for explaining it so simply!
Good to hear Dalbir!
Beautiful video
So if all the microservices could be written in their own language. How do the communicate? Do they usually send strings, json or some other protocol? Because remote method invocation would be difficult if they use different languages.
Through network using protocols such as HTTP or even lower-level such as TCP or UDP. Sometimes you go higher level and use GRPC wich uses HTTP2+ under the hood.
And you can use XML/JSON which is of course on HTTP.
Amazing explanation, thank you so much for this video.
Thank you for the explanation! Spectacular! 🙌
You're welcome, Donald, glad you found it useful!
THANK YOU! very clear and concise and well explained! make more of these videos plz!
Kind of odd that when I tried to watch this video as embedded in IBM's own microservices article I get the error, "Unauthorized domain: We're sorry, this content is only available on certain domains."
This is an amazing explaination. Thank you for making this video.
crystal clear. thanks!
Glad to have watched this. TY IBM!
understood it all nice explanation!
great big picture explanation
AMAZING explanation. really thank you .
Thank you!
Now THIS I understand! thanks!
The best explanation i have come across !
Thanks for watching, David!
Thank you very much for the much informative presentation in an easy understanding manner !
Great video and easy to understand -Monolith vs Microservices
This is the best explanation ever! Thank you!!!!
Perfect explanation sir
Simple and clear.
Thank you! 💪
Thanks for the explanation.
So basically modular web apps inside Docker containers?
Amazing explanation!
Thanks for sharing knowledge! :D
excellet explanation
Very apt and well explained. Thanks for this...
well articulated
nicely explained
Thanks a lot for this! Though I would like to ask, what is a DevOps pipeline? Any examples, please. Is it like a testing software? Please elaborate. Thank you.
Push code to branch in GH -> build that code (jenkins job start) -> test it -> deploy it (optionally, end of jenkins job)
there is one Pipeline example.
Nice explanation of Microservices
I miss the Challenge section for Microservices 🤪
Thank you, Geat explanation
Excellent video!
Thanks 😊
What is meant by hero deployment?
Very nice explanation, thanks!
Great topic, but you didn't mention the Challenge for the Micro Services
Great explanation! Thanks for sharing!
Thanks for watching, Olaf!
25 years ago there was Microsoft DCOM , Distributed Component Object Model (DCOM) Remote Protocol, a vision that failed
Excellent Explanation!
We're glad to hear this, Ann! Thank you for watching, Dan.
is the concept of infrastructure as a code a huge benefit for microservices architecture?
Hey, there! In short... yes! 🙂 Infrastructure as code (IAC) allows for consistent automated deployment of infrastructure which decreases manual errors and increases efficiency.
We have quite a few resources, too, if you'd like to explore more on this subject:
🎦 What is Infrastructure as Code (video): ibm.co/2OioRC5
▶️ Tutorial: ibm.co/3p09RoY
➡️ Article: ibm.co/3rDrQDz
@@IBMTechnology thank you , I will have a look :)
simple and quick
Thanks a lot
If you are a start up or even developing something in a company that hasn’t been validated should you really go ahead and build a micro service based architecture considering it’s more timely and expensive?
I’d rather build something quick and dirty and get it out to my customers and get feedback than spend time building a complex architecture that might not be relevant because our customers don’t want what we’re building.
Does anybody have an opinion on this?
thank u so much sir
Beautiful
I knew I hated Java applications for good reason. haha thanks for the great video.
CI/CD vs microservices?
Cool! IBM
I think the real world no real decoupling things. New business requirement come always caused changing from top to down, so here, it could be change required in thousand islands...
thanks!
Aws loadbalacer took me to MICROSERVICES and i am now here
Hero deployments... LOL, cool presentation, Very clear explanation thank you.
Everyone telling what are microservices but no one tells how to create microservices. 😢
WoW!
I really hope you're not writing on my screen with a sharpie
Nice try but no. The explanation is good but the benefits of the microservices architecture are not realistic - having multiple langs to deal with and maintain is a nightmare, infinite contracts and apis - instead of writing logics you write all that stuff (same bullshit as writing unit tests which create a false sense of everyting is ok). Most of the time microservices are not reusable. If a microservice is down youd probably want all your app to be down, because it creates a false sense that the app is running normaly which is not. There are other drawbacks which I dont want to describe as it becomes too long. The best approach is having a monolith (with heavy coupled logics) and few critical/exposed standalone and reusable services, which run long-running tasks.
There is no ideal solution especially when low talent is the norm.
This presentation is sadly very superficial. For any IT system, there are many different ways to allocate functionality to deployable units - ie there is a sliding scale from one company-wide monolith to a handful of larger systems to many smaller systems to truly function-level components. Each different level of granularity has its own advantages and disadvantages, and the optimal solution is likely to differ by business area - ie the optimal solution for a large system can well be a mix of components of different granularity. Very few large companies have a single monolith, and I doubt many companies use 100% fine-grained services either. Fine-grained components have some important advantages, but also some very nasty disadvantages. Moderate-grained components can potentially support elastic scaling without needing to be "single functions". What is presented here are truly two extremes, and while the disadvantages of huge monoliths are presented, the (many) problems with truly fine-grained systems are not discussed at all.
For 90% of companies, microservices are really a bad idea. Consultancy companies love to hype them because it drives demand for their services.
Microservice is more a disaster than a benefit, all just big talk echo chamber. Netflix did it now everyone wants to wear the fashion.
Of course IBM will emphasis microservices. More server thay can sell lol
But it hain't cheap :'(
I have no background in any of this so everything being said sounds like alien speak to me...