Microservice - an actor (actor model) implemented as a standalone asynchronous component, deployed in a container, communicating over platform independent communication channel, fulfilling a single or few functionalities of the total system.
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
This was one of the funniest things I've seen in a while. Story old as tech: a possible option depending on circumstances meets supervillain levels of greedy corporation and now you are a digital serf to Amazon because you implemented something someone called microservices but it meets almost none of the definitions or rationales for adopting given in this talk by one of its inventors/developers/practitioners/whatever.
22:36 - I've never understand the irony around Kubernetes or even Docker. Maybe that was humor of 2016-s? I don't know. But today in the 2020s no one laughs at it
People expect those tools to be some sort of magical answer to problems related to deployment and service management, before they realize it's not. That doesn't mean docker or k8s are not useful, not at all, it's just more complexity they're gonna need to introduce and master. Not to mention people who are using them for the wrong reasons...
@@mobe6524 Thank you for the clarification. Your answer really explains the meaning of Martin's irony at this point. I have worked quite a bit with container technologies, including Kubernetes. This is essentially a well-developed abstraction over the already existing ability in UNIX systems to package applications into containers. And I agree that these are difficult things to understand and require a high barrier to entry. But I would like to know what alternatives can be offered here as orchestrators in such complex systems based on microservices.
@@itcloudguy there isn't. He's just trying to bring people's attention on the topic. Like it's not just that simple and there is so much in there. You tend to hear a lot about the benefits but not much about the complexity behind. It's great to have the privilege of using modern tech such as docker and k8s, but how worth would that be? And that depends on the team and its skills and the project and the budget etc. etc.
![[XConf Brasil 2019] Martin Fowler - Introdução à Refatoração](http://i.ytimg.com/vi/TBHehDRuVCs/mqdefault.jpg)
Microservice - an actor (actor model) implemented as a standalone asynchronous component, deployed in a container, communicating over platform independent communication channel, fulfilling a single or few functionalities of the total system.
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
27:34 "Microservices often seem like the best way to organizing people." - Unfortunately, I tend to agree with that.
This was one of the funniest things I've seen in a while. Story old as tech: a possible option depending on circumstances meets supervillain levels of greedy corporation and now you are a digital serf to Amazon because you implemented something someone called microservices but it meets almost none of the definitions or rationales for adopting given in this talk by one of its inventors/developers/practitioners/whatever.
22:36 - I've never understand the irony around Kubernetes or even Docker. Maybe that was humor of 2016-s? I don't know. But today in the 2020s no one laughs at it
People expect those tools to be some sort of magical answer to problems related to deployment and service management, before they realize it's not.
That doesn't mean docker or k8s are not useful, not at all, it's just more complexity they're gonna need to introduce and master.
Not to mention people who are using them for the wrong reasons...
@@mobe6524 Thank you for the clarification. Your answer really explains the meaning of Martin's irony at this point.
I have worked quite a bit with container technologies, including Kubernetes. This is essentially a well-developed abstraction over the already existing ability in UNIX systems to package applications into containers. And I agree that these are difficult things to understand and require a high barrier to entry.
But I would like to know what alternatives can be offered here as orchestrators in such complex systems based on microservices.
@@itcloudguy there isn't.
He's just trying to bring people's attention on the topic. Like it's not just that simple and there is so much in there.
You tend to hear a lot about the benefits but not much about the complexity behind.
It's great to have the privilege of using modern tech such as docker and k8s, but how worth would that be?
And that depends on the team and its skills and the project and the budget etc. etc.