Комментарии:
Amazing explanation!
Ответитьclear explanation of complex concept in understandable manner
ОтветитьThere is no ideal solution especially when low talent is the norm.
Ответитьsame tiring incorrect explanation
Ответить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.
Ответитьgreat big picture explanation
Ответитьgreat video, thanks 😊
ОтветитьWhat is meant by hero deployment?
ОтветитьVery clear and helpful explanation. Just the right pace and amount of information.
Ответить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?
But it hain't cheap :'(
ОтветитьBeautiful video
ОтветитьNice job, Dan. Good seeing you again!
ОтветитьI have no background in any of this so everything being said sounds like alien speak to me...
ОтветитьAwesome explanation - Thank you
ОтветитьAmazing explanation best one I’ve seen so far
ОтветитьOMG best explaination ever!
ОтветитьI miss the Challenge section for Microservices 🤪
ОтветитьOf course IBM will emphasis microservices. More server thay can sell lol
Ответитьso bright and clear explanation !
ОтветитьSimple, interesting and example-based explanation. Thanks!
ОтветитьThis is an amazing explaination. Thank you for making this video.
ОтветитьThe video is bad. It literally says: a monolith has only disadvantages and microservices have only advantages. Too bias
ОтветитьAMAZING explanation. really thank you .
ОтветитьThanks for making these concepts so easy to understand.
ОтветитьGreat topic, but you didn't mention the Challenge for the Micro Services
ОтветитьSo, that is very similar to the way of using nodes in ROS
ОтветитьAmazing explanation, thank you so much for this video.
ОтветитьVery straight forward and easy to follow. Great video.
ОтветитьEveryone telling what are microservices but no one tells how to create microservices. 😢
ОтветитьCI/CD vs microservices?
ОтветитьAws loadbalacer took me to MICROSERVICES and i am now here
Ответить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?
ОтветитьTHANK YOU! very clear and concise and well explained! make more of these videos plz!
Ответитьthank u so much sir
ОтветитьThanks 😊
ОтветитьVery helpful video! Also this reminded me how much I love lightboards
ОтветитьVery awesome video with perfect notes. thanks...
ОтветитьFor 90% of companies, microservices are really a bad idea. Consultancy companies love to hype them because it drives demand for their services.
Ответить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.
ОтветитьWhat a fanstastic, smart presentation!
ОтветитьPerfect explanation sir
ОтветитьBeautiful
ОтветитьCool! IBM <3
Ответитьcrystal clear. thanks!
Ответить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...
Ответить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.
ОтветитьThank you!
ОтветитьBest video on microservices
Ответить