4 ms·

Like most articles in distributed systems, this makes wild assumptions about the most important, i.e. the human layer. I would bet $100 that this is written by

Like most articles in distributed systems, this makes wild assumptions about the most important, i.e. the human layer. I would bet $100 that this is written by the same sort of person who thinks "Managers – what do they do all day exactly?" [1] > If you hire the best engineers.... Guess what, there is no broad consensus on what "best engineer" means. I bet your org is rejecting really good engineers right now because they don't know what Kubernetes is. Same goes for literally any other technology that has been part of a hype cycle (Java in 2001, Ruby on Rails in 2011, ML in 2011; no the precise years don't matter). > ...trust them to make the best decisions. A lot of work encapsulated there in less than ten words. If you hire a bunch of people and tell them "you are the best", you think they are going to sit around and run the Raft protocol for consensus on deciding how to architect the system? No, each of them is going to reinvent Kubernetes, and likely not in an amazing way. Microservices are often best deployed when there is a mixture of cultural and engineering factors that makes it easy to split up a system into different parts that have interfaces with each other. It has little to do with the superiority of the technical architecture. ---------------------------------------- [1] Looks like the article was written by the CTO of Amazon, which...surprises me a bit. Then again, from all accounts, Amazon's not exactly known as the best place to work; so maybe I'm right? In any case, anything written by Amazon is not directly applicable to the vast majority of small-to-medium companies.

deleted 3y ago
[deleted]
jabradoodle 3y ago
Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. Also, they never claimed technical superiority of microservices, quote: > For example, a startup with five engineers may choose a monolithic architecture because it is easier to deploy and doesn’t require their small team to learn multiple programming languages.
- quadrifoliate 3y ago
  > Also, they never claimed technical superiority of microservices, quote: No, but they are arguing against the strawman of the perceived technical inferiority of monoliths. Look at the title of the article. I am simply calling out that strawman as such. If they wanted to convey the message of "It all depends, use the best architecture for the job", they should reflect that in the title.
  - jabradoodle 3y ago
    Maybe we have radically different experiences, I don't see that as a strawman, the industry as I have seen it largely does view microservices as superior.
- Aeolun 3y ago
  > Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. That’s weird. Any time I’ve seen anyone let their engineers engineer, those engineers have immediately started following the hype.
  - sopooneo 3y ago
    I have many times seen management hire what they thought were "the best engineers" and let them completely loose for months or years straight to eventually deliver... nothing. Literally nothing. Or at least nothing that actually works in any way.
musicale 3y ago
> Managers – what do they do all day exactly? In companies I'm familiar with projects are run by technical leads and product leads. Managers don't interact with anyone doing actual work, which is probably for the best.

deleted 3y ago

[deleted]

jabradoodle 3y ago

Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. Also, they never claimed technical superiority of microservices, quote: > For example, a startup with five engineers may choose a monolithic architecture because it is easier to deploy and doesn’t require their small team to learn multiple programming languages.

quadrifoliate 3y ago
> Also, they never claimed technical superiority of microservices, quote: No, but they are arguing against the strawman of the perceived technical inferiority of monoliths. Look at the title of the article. I am simply calling out that strawman as such. If they wanted to convey the message of "It all depends, use the best architecture for the job", they should reflect that in the title.
- jabradoodle 3y ago
  Maybe we have radically different experiences, I don't see that as a strawman, the industry as I have seen it largely does view microservices as superior.
Aeolun 3y ago
> Their point on hiring the best engineers was specifically about not following the hype, and allowing engineers to engineer. That’s weird. Any time I’ve seen anyone let their engineers engineer, those engineers have immediately started following the hype.
- sopooneo 3y ago
  I have many times seen management hire what they thought were "the best engineers" and let them completely loose for months or years straight to eventually deliver... nothing. Literally nothing. Or at least nothing that actually works in any way.

musicale 3y ago

> Managers – what do they do all day exactly? In companies I'm familiar with projects are run by technical leads and product leads. Managers don't interact with anyone doing actual work, which is probably for the best.