Hi all, this is the article:
http://blogs.gartner.com/gary-olliffe/2017/01/31/what-a-microservice-is-not/
My quick comments for the following NOT Microservices:
- A simple API to a more complex service implemented as part of a monolithic application {MP: how one would know that the service is complex and monolithic, and why one would care about this?}
- A service implemented with a small amount of code – it could be a microservice, but a small amount of code may still be coupled to other code and services or not be independently deployable. {MP: since when an amount of code matters?}
- A service built and delivered without automation of testing and deployment and operations {MP: totally crap - who on the earth cares what it automatically tested or not?}
- A service built on mutable compute infrastructure that is updated and patched separately from software deployment {???}
- A service that has dependencies on its peers that prevent it from being changed and updated independently {Wow! Microservices are NOT services at all!!!}
- A large, coarse-grained service or monolithic set of services packaged in a Docker container {???}
- A service exposed via API by another party (no matter how it is implemented, if you don’t control the implementation, this is just a service, as far as your application is concerned) {Nice}
- A component, module, service or capability, labeled as a “microservice” by a vendor, over which you do not have deployment and management control consistent with your (real) other microservices {Finita la comedia...}
And last but by no means least…
- A published API – microservice architecture is an implementation detail that should be separated from the published interface specification {MP: when you last time heard that Microservice is implementation rather than an interface?}
Regards,
- Michael