| > By which I mean in the context of the article, which I think dismisses microservices as a potential solution with prejudice > What I seem to be coming up against when discussing this is people conflate worthwhile evaluation with worthwhile solution. > It doesn't equate to saying microservice is the solution if it meets that one criteria, only don't rule it out. I read the article, it's not against microservice architecture itself, but points out that you shouldn't treat them as a starting point or a best practice. There is even a section named "When Microservices Do Make Sense".
It also highlights examples where microservices make sense ("Their post is a good example of how microservices can work when you have the organizational maturity and operational overhead to support them."), so I really do not see where does anyone rule out, dismiss, come up against anything. I somewhat understand and agree what you are trying to argue against, but that's definitely not in this article. > Its a good rule of thumb that you may want to evaluate if a microservice is appropriate. This is too general to be practically useful — it applies to almost everything in life. |