5 ms·

The author does not seem to understand when to correctly apply microservices. There are two basic use cases: 1) Different parts of your solution have different

by dcwca 7y ago

The author does not seem to understand when to correctly apply microservices. There are two basic use cases: 1) Different parts of your solution have different load patterns and it is economically beneficial to scale them at different rates and 2) Different teams need to be able to work & ship autonomously. It's not at all about technical merits or architectural beauty. It's about people and costs.

Glyptodon 7y ago
I kind of think the items (1) and (2) you list don't automatically mean micro-services, so much as they mean separation of concerns can be beneficial. Isn't there room for a middle ground with modularity that can live in between a full blown monolith or a full blown microservices pattern, particularly for operations that are more medium scale?
- mikkergp 7y ago
  megaservices
- FlorianRappl 7y ago
  Of course there is, was, and will be! I think people sometimes forget that a healthy level of pragmatism is what keeps shipping. Just because someone said "microservices is the new all" you don't need to do it. Just because some said "monoliths are the future" it does not have to be true for you. Take all these as case studies and solutions that apparently worked under specific conditions.
- unlinked_dll 7y ago
  Yea just take the ideas that apply to your problem domain and implement them in a way that's sane. Design/architecture patterns are much more useful as templates to be specialized for your problem. I really don't like the dogmatic view of architectures. Leaves no room for craftsmanship, and it's only really useful for creating code monkeys that have to follow a spec and need to be interchangeable cogs in the machine.
peteforde 7y ago
The author is a Kubernetes expert, so perhaps you are the student and not the master? https://github.com/kelseyhightower/kubernetes-the-hard-way https://github.com/kelseyhightower/kubernetes-the-hard-way
- bastardson 7y ago
  A person’s perceived status shouldn’t win them an argument.
  - cc81 7y ago
    No, but the dude works at google and has written that and other books about Kubernetes so obviously he knows about scaling parts of a system and huge organizations working on software together. That is not what he is commenting on here though. It is that microservice architecture is starting to become the default pattern on how to build applications for a lot of people. Instead it should be an exception when you reach those very specific problems that most people don't have.
  - peteforde 7y ago
    I didn't declare their argument won, lost or invalid. I did suggest that they consider the bona fides of the person whose opinion they were tossing off as uneducated. Thanks for the downvote, though.
    - bastardson 7y ago
      > I did suggest that they consider the bona fides of the person whose opinion they were tossing off as uneducated. It would be more constructive to give reasons why one argument is better than another though, rather than resorting to status, and you did not reference any of the commenter’s points. > Thanks for the downvote, though. I don’t have the karma required to give a downvote. I’m not sure who you should thank.
      - peteforde 7y ago
        Honestly, you're missing or avoiding my point: I'm not deferring to the author because he's respected or has a popular blog. I am suggesting that the OP has little business writing off a legitimate expert's opinion in a domain where they are highly qualified to comment. This isn't controversial. If you had the karma to downvote, would you give a hard time to the OP who started with "The author does not seem to understand when to correctly apply microservices."?

by dcwca 7y ago

Glyptodon 7y ago

I kind of think the items (1) and (2) you list don't automatically mean micro-services, so much as they mean separation of concerns can be beneficial. Isn't there room for a middle ground with modularity that can live in between a full blown monolith or a full blown microservices pattern, particularly for operations that are more medium scale?

mikkergp 7y ago
megaservices
FlorianRappl 7y ago
Of course there is, was, and will be! I think people sometimes forget that a healthy level of pragmatism is what keeps shipping. Just because someone said "microservices is the new all" you don't need to do it. Just because some said "monoliths are the future" it does not have to be true for you. Take all these as case studies and solutions that apparently worked under specific conditions.
unlinked_dll 7y ago
Yea just take the ideas that apply to your problem domain and implement them in a way that's sane. Design/architecture patterns are much more useful as templates to be specialized for your problem. I really don't like the dogmatic view of architectures. Leaves no room for craftsmanship, and it's only really useful for creating code monkeys that have to follow a spec and need to be interchangeable cogs in the machine.

peteforde 7y ago

The author is a Kubernetes expert, so perhaps you are the student and not the master? https://github.com/kelseyhightower/kubernetes-the-hard-way https://github.com/kelseyhightower/kubernetes-the-hard-way

bastardson 7y ago
A person’s perceived status shouldn’t win them an argument.
- cc81 7y ago
  No, but the dude works at google and has written that and other books about Kubernetes so obviously he knows about scaling parts of a system and huge organizations working on software together. That is not what he is commenting on here though. It is that microservice architecture is starting to become the default pattern on how to build applications for a lot of people. Instead it should be an exception when you reach those very specific problems that most people don't have.
- peteforde 7y ago
  I didn't declare their argument won, lost or invalid. I did suggest that they consider the bona fides of the person whose opinion they were tossing off as uneducated. Thanks for the downvote, though.
  - bastardson 7y ago
    > I did suggest that they consider the bona fides of the person whose opinion they were tossing off as uneducated. It would be more constructive to give reasons why one argument is better than another though, rather than resorting to status, and you did not reference any of the commenter’s points. > Thanks for the downvote, though. I don’t have the karma required to give a downvote. I’m not sure who you should thank.
    - peteforde 7y ago
      Honestly, you're missing or avoiding my point: I'm not deferring to the author because he's respected or has a popular blog. I am suggesting that the OP has little business writing off a legitimate expert's opinion in a domain where they are highly qualified to comment. This isn't controversial. If you had the karma to downvote, would you give a hard time to the OP who started with "The author does not seem to understand when to correctly apply microservices."?