3 ms·
Microservice implies systems that are decoupled for deployment purposes. For example, Microservice A could restart to a new version while Microservice B keeps r
by cturner 6y ago
Microservice implies systems that are decoupled for deployment purposes. For example, Microservice A could restart to a new version while Microservice B keeps running. This is a more complicated interaction contract than services where their deployment is coordinated in concert.
- xorcist 6y agoBut this was true in the middleware type of products too, and you can't get more monolithic than that.
- brown9-2 6y agoI don’t think this is accurate. I’ve worked at companies that did “service-oriented architecture” long before the rise of the term “microservice” and it was clearly recognized that different “services” shouldn’t be so coupled together you can’t redeploy them separately.
- deleted 6y ago[deleted]
- scaryclam 6y agoYes, you're right. A system that requires services to be deployed together is just a distributed monolith.
- cturner 6y agoThis thread considered an issue: whether services and microservices are equivalent concepts. They are not. There is a quality that is held by Microservices, yet which is not universally held by Services. You have observed that other services also have that quality. Indeed. Nowhere did I say, "all services with decoupled deployment are microservices".
- cturner 6y agoRevisit. I can where brown9 is coming from. I could have avoided leaving that interpretation open by writing, "here is an example of a quality that is held by all X, yet not by all Y".